cross-posted from: lemmy.bestiver.se/post/1033182
They used to just hit 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 4 weeks 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.ca 4 weeks 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 4 weeks 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.
grey_maniac@lemmy.ca 4 weeks ago
I don’t use windows that much anymore, but couldn’t you make it a read-only file?
MonkderVierte@lemmy.zip 4 weeks ago
From what i remember, the user has to disable some safeguards, to be able to modify it.