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

Any on-device solution that simply sends back a yes/no result as you describe is guaranteed to have one of two problems:

1) It is vulnerable to modifications and hacks on the local device that get it to send back a "yes" result without actually verifying anything

OR

2) It requires the device to use some kind of closed, proprietary system that allows the service to guarantee that #1 cannot happen

Now, in general, the tech world is pretty happy to accept #2, but many of the people around here would object to it on very reasonable grounds.





I think that the improved version of age verification is to ask the yes/no question to a government third party based on a signed payload that your local device offers the service. The government already has your identifying data, they only need to certify on behalf of which person the question is asked.

So then you're just back to the even more basic problem of "is the person using this device the same person that the payload was signed on behalf of?"

Yep. But in my mind that's being mitigated by the real measure for identity proof, which is some type of electronic ids.

Which a) has a whole host of other concerns associated with it, and b) still does not solve that problem, because it's not at all hard for a child (especially a teenager!) to sneak their parent's ID, use it to authenticate for a service, then put it back.

After all, are most services going to require the ID to be present for every session? Or are they going to require a one-time authentication for the account?


I don't want it in my hardware but I'd buy an accessory that does this.

Would you be OK with everyone who wants to browse the web unhindered being required to buy an accessory that does this...?

And if it’s such a high adoption rate for an “optional” accessory, may as well just build it right in…

Oh look, we’re back where we started. The only winning move is to not play.


I mean most mobile devices have already accepted closed ROMs in their baseband and all/most browsers that try to interact with streaming sits require Widevine . As longas its going to hapen one way or another better it be local , and not a gov thing or a monopoly.

At the end of the day the tool should be there enforcement down to the relevant local authorities or not.


OK, but what about your desktop computer?



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

Search: