Adobe secretly modifies your hosts file for the stupidest reason – OSnews
www.osnews.com
  • sirblastalot@ttrpg.network
    3·
    2 days ago

    They used to just hit http://localhost/:<various ports>/cc.png which connected to your Creative Cloud app directly, but then Chrome started blocking Local Network Access, so they had to do this hosts file hack instead.

    Ok but adobe what if you didn’t portscan me either, please.

  • Vince@lemmy.world
    25·
    3 days ago

    Interesting, considering one of the ways to prevent Adobe from phoning home was to redirect their domains via hosts file. Perhaps that’s where they got the idea, or one of the things they added, like hey were already looking at your hosts file to check for piracy, might as well add some entries for other reasons.

    • floofloof@lemmy.caOP
      33·
      3 days ago

      I’m trying to think of legitimate reasons why an installer should be able to edit that file, and I can’t think of any. Seems like the OS should lock it down.

      • hoshikarakitaridia@lemmy.world
        11·
        3 days ago

        Yeah from my intuition it sounds like this file serves as a makeshift firewall / proxy. Allowing software to override it kinda makes this weak and basically useless for a lot of purposes.

        • azuth@sh.itjust.works
          3·
          3 days ago

          It’s a DNS override. DNS is what turns URL addresses (www.Lemmy.org) to IP addresses (127.1.0.42) which are what is used to actually connect to another computer.

          Normally your PC asks a DNS server,usually provided by your ISP by default, unless there is an entry in the hosts file.

          So authorities often ‘block’ websites by just asking ISP to not return the true IP for a URL. You can get around that by putting the IP in your hosts file. You can also block websites by adding an entry on your hosts file that point to local host (your PC).

        • hoshikarakitaridia@lemmy.world
          6·
          3 days ago

          Tbf it’s already write for admins only. But, if you completely remove write access that makes the file itself obsolete (there’s no use in a file that no one can edit) and if you restrict it to trusted installer / verified software, that’s not gonna eliminate Adobe.

  • Kissaki@programming.dev
    3·
    3 days ago

    Interesting, clever technical workaround for (potentially) real user benefit. But still, they should never do that. Working around safeguards and system component borders for user convenience is a very bad idea and practice.