5 ms·
Do these cryptographic tools prevent the government entity providing them from knowing which websites verify your age? If not, then that's too much Uncle Sam wa
by stvltvs 2y ago
Do these cryptographic tools prevent the government entity providing them from knowing which websites verify your age? If not, then that's too much Uncle Sam watching over your shoulder as you watch your porn.
- quotemstr 2y agoYes, they do precisely that, and in a way that depends only in math and cryptography. No possibility of leaking some naughty list after a hack.
- stvltvs 2y agoCan a malicious gov site gather a list of which sites are asking for your verification?
- some_furry 2y agoIt depends on the tool. https://zkdocs.com https://zkdocs.com has some protocols described, if you're curious to learn more about this space.
- Izkata 2y agoFor a simple example, a JWT doesn't need to be done with shared secrets, and can instead use RSA private/public keys. The payload could contain just two fields like "issued" (to ensure the token isn't shared and reused) and "age" (what you want to share), you'd be able to decode the payload to see what's in it and know there's no identifying information, and the government site would provide the public key allowing anyone (like a porn site) to verify the JWT hasn't been tampered with without knowing who it was that got the JWT.
- stvltvs 2y agoCan the gov site see who requests age verification? They already have to know who they're verifying because how else would they verify age?
- Izkata 2y agoYes, but the idea is they wouldn't know why or for what site. In the JWT version I'm imagining, the porn site would say "go to your government website, generate this token, then copy/paste it here". There's no connection between the porn site and government site, and if the public key was retrieved and cached earlier there isn't even a timing-based way to connect them.
- some_furry 2y ago(JWT in general is a bad solution, but let's ignore that for the sake of discussion.) I think you're severely underestimating the efficacy of traffic analysis and correlation efforts. PrivacyPass is a better starting point, IMHO. The Cwtch developers (Open Privacy) even implemented PrivPass over Ristretto255, which is objectively awesome.
- stvltvs 2y agoDidn't find many details, so please excuse the questions. So the user would get a number of signed tokens from the gov to prove age, then a token could be shared with a site that verifies age without connecting to gov, assuming it's already aware of the gov's public key? What prevents the same token from being used by more than one person? How can the site prove compliance with the law? Will they need to store the tokens for each user? Can the gov tie a stored token back to a particular person that that verified?