3 ms·
I think the problem runs deeper than you're considering. The entire purpose of this service, as you're describing it, is to allow web sites to access informatio
by duskwuff 10y ago
I think the problem runs deeper than you're considering. The entire purpose of this service, as you're describing it, is to allow web sites to access information on what other sites their users have visited (and, presumably, to read "reputation" annotations made by those sites), and to use that to make access control decisions. The privacy violations involved are inherent to that purpose; you can't wipe them away by throwing "but with encryption" at the problem.
- kakarot 10y agoI don't mean to shut down your criticism, but how does it present a vulnerable security model?
- duskwuff 10y agoPrivacy is a component of security. Systemically violating your users' privacy is a security issue -- period. If your "security models" don't recognize this as an issue, you need to change those models.
- kakarot 10y agoPrivacy and security are two separate domains. But even then, how does this violate anyone's privacy in any way that existing authentication protocols do not?