With many jurisdictions introducing age verification laws for various things on the internet, a lot of questions have come up about implementation and privacy. I haven’t seen anyone come up with a real working example of how to implement it technically/cryptographically that don’t have any major flaws.

Setting aside the ethics of age verification and whether or not it’s a good idea - is it technically possible to accurately verify someone’s age while respecting their privacy and if so how?

For an implementation to work, it should:

  • Let the service know that the user is an adult by providing a verifiable proof of adulthood (eg. A proof that’s signed by a trusted authority/government)
  • Not let the service know any other information about the user besides what they already learn through http or TCP/IP
  • Not let a government or age verification authority know whenever a user is accessing 18+ content
  • Make it difficult or impossible for a child to fake a proof of adulthood, eg. By downloading an already verified anonymous signing key shared by an adult, etc.
  • Be simple enough to implement that non-technical people can do it without difficulty and without purchasing bespoke hardware
  • Ideally not requiring any long term storage of personal information by a government or verification authority that could be compromised in a data breach

I think the first two points are fairly simple (lots of possible implementations with zero-knowledge proofs and anonymous signing keys, credentials with partial disclosure, authenticating with a trusted age verification system, etc. etc.)

The rest of the points are the difficult ones. Some children will circumvent any system (eg. By getting an adult to log in for them) but a working system should deter most children and require more than a quick download or a web search for instructions on how to circumvent.

The last point might already be a lost cause depending on your government, so unfortunately it’s probably not as important.

  • TechLich@lemmy.worldOP
    link
    fedilink
    arrow-up
    1
    ·
    2 hours ago

    It would also reveal to the government that the user was accessing 18+ content (though not what that content is if the token is blinded).

    It also doesn’t stop the easy circumvent of someone who is an adult providing a service for children or others who don’t want to auth with the government.

    1. The 18+ site provides Child c with a token T and it’s blinded to b(T)
    2. The child sends b(T) to a malicious service run by a real adult (Mal)
    3. Mal sends the token to the AVS to create s(b(T))
    4. Mal provides s(b(T)) to the child who gives it to the 18+ site as a legit S(T)