News for hackers. Stuff that matters.
Re:Hardening Firefox – a checklist for improved browser privacy by ranger_danger on Saturday August 30, 2025 @01:28PM (#45076429)
> JS, and several other components, if its active will negate a lot of the defenses that have been developed to-date.

I thought if you disabled JS, then that would greatly narrow down which user on the internet you are, since very few people (in comparison to everyone else in the world) actually do this.

> not authorized by the owner of the SAN being visited

Source?

> TLS can't be trusted

Do you have more info on this? Why are more people not worried about it?

Re:Hardening Firefox – a checklist for improved browser privacy by trod1234 on Saturday August 30, 2025 @04:04PM (#45077575)
> I thought if you disabled JS, then that would greatly narrow down which user on the internet you are...

It is a fundamentally cursed problem that has a lot of nuance.

You have buckets of people, and the entropy or difference between your collected artifacts and others must be sufficient to uniquely identify a single person, that is the point of fingerprinting. Your natural defense is in not sticking out of that group/crowd uniquely so others in the group may carry the same range of fingerprints.

At the same time, if you homogenize the artifacts to limit it down to a single fingerprint the sites will simply deny access.

Disabling JS altogether doesn't identify you aside from the fact that you are part of the overall group that has it disabled, the trade-off is that all the entropy JS would normally collect cannot be collected. So while they cannot identify you uniquely they can identify the group by denying that group, and that is the fundamental weakness of binary switches. Its a constant cat and mouse.

> not authorized by the owner of the SAN being visited. > Source?

Firsthand experience with a large VOIP provider where communications would fail intermittently but in targeted ways that avoid common test failures. Call tests would intermittently but routinely fail in the silent-fail domain of interrupt driven calling (where you wouldn't know a call was inbound), and the failures would occur only in that domain. The issues were narrowed down to a mismatch in certificates through a lengthy support correspondence where the hosted certificate vs what was being provided at the edge were different. The artifacts were compared manually through correspondence.

The certificate revocation was revoked within 48h once the vendor reached out to Google, but we've seen it happen twice now. The standards in general use don't have a means aside from revocation to handle bad-acting at the root-PKI level. Chain of trust issues like this have been known about for over 2 decades in the respective fields.

> Do you have any more info on this? Why are more people not worried about it?

On the specifics? The Princeton Raptor attack paper (2015) covers the details. Early termination of encryption, and traffic analysis are pretty bad.

Why more people aren't worried? I suppose its because most of the security industry (not all) has accepted the fact that device security is porous, and there isn't really much you can do to hold the manufacturer responsible or to make changes. Surveillance capitalism is also incentivized through profit motive to impose a state of complete and total dependency/compromise.

The state of security today, with your almost routine data breaches every quarter, is a direct consequence from lack of liability, accountability, and regulation.

The breadth and depth of scale is enough to drive one a bit crazy, and people are largely powerless to mitigate the issues as most of the market is silently nationalized in one form or another. Its no longer about the features people need, but about coercing the market where the only choice is what gets shoveled.