the linkedin fingerprinting you and scanning your extensions thing is a pretty good example of just how much js leaks about your browserhttps://browsergate.eu/how-it-works/

[rebane2001@infosec.exchange]

the linkedin fingerprinting you and scanning your extensions thing is a pretty good example of just how much js leaks about your browser
https://browsergate.eu/how-it-works/

[rebane2001@infosec.exchange]

i feel obliged to add some context to the link i shared:
https://bsky.app/profile/william-oconnell.bsky.social/post/3mil3dtznwc2u

[aura@gts.foxsnuggl.es]

@rebane2001 reminds me of the old "try loading a remote resource (via css if you're sneaky) and see if it gets served from cache based on timing" fingerprinting tricks.

[stefanlindbohm@mastodon.social]

@rebane2001 @bovine3dom Chrome specifically though. Most other browsers have better privacy protections.

[bovine3dom@masto.ai]

@stefanlindbohm I'm pretty sure the DOM walking works in all browsers. Less sure about fetching extension resources

of course, apps are a million times worse...

@rebane2001