3 ms·
To me, a good solution would be a chip-based smart card with a private key on it for physical proof of identity, and an oauth api for web based stuff. The api w
by tomschlick 9y ago
To me, a good solution would be a chip-based smart card with a private key on it for physical proof of identity, and an oauth api for web based stuff. The api would also power the back-end of the in person transactions and issue the vendor a token which they would use from that point forward.
In this system, everything would be logged in terms of who/what accessed your data and it could be de-authorized at any point.
The cards themselves could just be each state's ID/Drivers License to avoid the scare of the national id that many are opposed to for one reason or another. Replacing an ID would be as easy as visiting your DMV (shudder) and them invalidating your old private key.
- chatmasta 9y agoYou would rather the government store 300 million identifiers instead of Equifax? There are crypto solutions to this problem, but they’re not as simple as symmetric encryption and smart cards. An ideal system will also enforce rules for storage and access. Something like your data is always encrypted with your own private key, and you can authorize bits of the data at a time to third parties.
- tomschlick 9y agoNo, the government wouldn't store anything other than the basic identity (which they already do) and issue verification tokens. The accessor would store their proprietary info as well as the access token to person's private info on the govt api. Full blown crypto solutions to this don't really scale well and present many problems where the accessor would need to keep asking you for info to see if it changed. My solution solves the main problem of having a universal number that can get your identity stolen. If we can fix that we have solved 90% of the problem and can work on other things like privacy of said data at a later date.