In response to 0.0.0.0 day, Firefox Nightly version 131 had introduced a new security measure: blocking access to 0.0.0.0/::/::ffff:0.0.0.0 addresses. This change is currently live for Nightly users and will be gradually rolled out to all release users in the near future. Before we implement this ch...
  • Dave@lemmy.nz
    5·
    8 hours ago

    The linked blog post explains about the vulnerability, I thought it was quite interesting.

  • MangoPenguinEnglish
    23·
    14 hours ago

    I didn’t even realize 0.0.0.0 was a valid address to enter into a browser! TIL.

    • Possibly linux@lemmy.zipEnglish
      28·
      14 hours ago

      On Linux it is just a catch all address (listen on all interfaces)

      Elsewhere it doesn’t do anything since I don’t believe it is part of the networking standards

      • MangoPenguinEnglish
        13·
        14 hours ago

        Yeah I’m familiar with that part, I just meant in context of a browser being able to connect to it.

        • sugar_in_your_tea@sh.itjust.works
          2·
          3 hours ago

          If I were implementing it, I’d just list all interfaces on the machine and see if there’s a service bound to it on the given port. There’s probably only one, but it’s technically undefined behavior I think.

  • RedWeasel@lemmy.worldEnglish
    21·
    2 hours ago

    I just wish they’d stop blocking http requests on lan addresses honestly.

    Thanks for the suggestions. While I was investigating I ended up looking and had a proxy issue. Obviously a problem on my part.

    • flux@lemmy.mlEnglish
      3·
      7 hours ago

      Do you have standard Firefox with default options that does this? This has not been my experience.

      You could try out with a new profile if it works out the same.

      • RedWeasel@lemmy.worldEnglish
        1·
        2 hours ago

        Try the Firefox Developer version. No addons.

        EDIT: Thanks for the suggestions. While I was investigating I ended up looking and had a proxy issue. Obviously a problem on my part.

          • RedWeasel@lemmy.worldEnglish
            1·
            3 hours ago

            Unable to connect

            Firefox can’t establish a connection to the server at 192.168.2.210.

            The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox Developer Edition is permitted to access the web.

            I don’t see an error in the log about the specific page I am trying to access, but another had a link to https://support.mozilla.org/en-US/kb/https-only-prefs

            • Possibly linux@lemmy.zipEnglish
              2·
              2 hours ago

              I don’t think they ware going to start disabling http. Http is needed in a lot of cases to get https plus there are still use cases for http like testing.

              Have you fired up Wireshark and looked at what port it is connecting to?

              • RedWeasel@lemmy.worldEnglish
                1·
                2 hours ago

                Thanks for the suggestions. While I was investigating I ended up looking and had a proxy issue. Obviously a problem on my part.

    • sugar_in_your_tea@sh.itjust.works
      2·
      3 hours ago

      0.0.0.0 binds to all addresses on the machine for servers, but I don’t know what a browser would do when trying to resolve it. I guess look at all addresses on the machine and see if anything has bound to the indicated port on that address? First one it finds wins?

  • HubertManne@moist.catsweat.com
    5·
    14 hours ago

    seriously. I like the federation but people way overuse the spoiler tag or nsfw or whatever. I usually skip over but had to vent. Oh uh. ankle in this one. better make sure no one gets fired over it.

      • HubertManne@moist.catsweat.com
        1·
        54 minutes ago

        curiously someone asked me about it but before I could answer as it was my overnight a whole chain went up with folks that solved the mystery. Its something that for some reason is not showing between lemmy and mbin. So mbin users should (not) see it while presumably lemmy users will not realize the tag is there. Honestly I would like mbin to allow me to ignore the tag but apparently saying show nsfw just means the feed will show but it does the tag thing. Don’t get me wrong I would use it but only if users kept to to blocking just completely graphic stuff. I would rather see the graphic stuff than the rediculously mild stuff that gets blured. Maybe its mbin users with the dainty feelings.

  • Eager Eagle@lemmy.worldEnglish
    6·
    14 hours ago

    Fine by me. I self-host a lot of stuff but never used 0.0.0.0 for browsing, so I just disabled it here to try it out.