Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think the DBSC is on the right direction but while it generates separate keys per session to prevent cross-session tracking (Google's ultimate ad dream), the spec acknowledges a critical vulnerability: malicious sites can collaborate by attempting to guess public keys until they find matches, creating persistent cross-site user identifiers, essentially weaponizing the security feature into the ultimate tracking system that survives cookie deletion and VPN usage


How long are the public keys? >160 bits and that's futile.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: