- cross-posted to:
- privacy@lemmy.ml
- privacy@lemmy.ca
- privacy@lemmy.ml
- cross-posted to:
- privacy@lemmy.ml
- privacy@lemmy.ca
- privacy@lemmy.ml
Microsoft is running one of the largest corporate espionage operations in modern history. Every time any of LinkedIn’s one billion users visits linkedin.com, hidden code searches their computer for installed software, collects the results, and transmits them to LinkedIn’s servers and to third-party companies including an American-Israeli cybersecurity firm.
First comment from the link:
Every time you open LinkedIn in a Chrome-based browser, LinkedIn’s JavaScript executes a silent scan of your installed browser extensions. The scan probes for thousands of specific extensions by ID, collects the results, encrypts them, and transmits them to LinkedIn’s servers.
That is very different from “searches their computer for installed software”
Still don’t really understand why browsers expose this data to sites.
Web browsers are just such a massive security hole.
On the contrary, websites are incredibly sandboxed. It’s damn near impossible to find out anything about the computer. Off the top of my head: Want to know where the file lives that the user just picked? Sure, it’s C:\fakepath\filename. Wanna check the color of a link to see if the user has visited the site before? No need to check. The answer will be ‘false’. Always.
Here’s the information a web server needs to deliver content to a browser:
- The requested resource
- An IP address
- User credentials (sometimes)
Everything else is a fucking security hole. There’s no good reason for servers to know what extensions you have installed, what OS you’re running, the dimensions of your browser window, where your mouse cursor is positioned, or any one of a thousand other data points that browsers freely hand over.
There are absolutely reasons. Firefox is done by a reasonable job of anti-fingerprinting, and it’s a fine line to walk to disable as many of those indicators as possible without breaking sites.
Browsers do give away too much, but at least Firefox is working on it. And it’s not extremely straightforward.
That sounds… normal? and maybe even sensible, especially if LinkedIn does SSR, since that could allow the servers know how to tailor the content to the specific browser requesting a page.
In what fucking world is it “normal” or “sensible” to scan your browser extensions to decide how to render a page? Please explain.
I’ve been doing web development for 30 years (since the time when “SSR” was just called “building a web app”) and I have not once ever had the desire or need to do this.
And yet the thread you linked says they are scanning for browser plugins.
Which is very different from scanning our computers…
Right? It describes some fingerprinting techniques the site uses, but browser sandboxing limits the available data.
This type of scan is uncommon, and slightly more invasive than other tracking techniques, but neither new nor urgent.
It doesn’t paint the site operator as a paragon of privacy for sure tho.




