3 ms·
Have a unique public identifier for everyone. An identifier is not a verifier. Just because I know my neighbors id number doesn't mean I can e.g open a bank ac
by alkonaut 9y ago
Have a unique public identifier for everyone.
An identifier is not a verifier. Just because I know my neighbors id number doesn't mean I can e.g open a bank account in his name.
The act of validating that you are the person with the given ID requires some form of id validation (drivers license, passport, digital id).
I can't even understand how you even keep a reliable customer database that works through name and address changes without having a single immutable identifier for everyone. I can understand how people started using SSN if that is the only number there is.
Here I just record bob the customer as 123467890 and he can change name, address etc all he wants without telling me. I can still send him his bill because I can lookup both a name and address for any id at any point in time by just asking the tax- (and id-) authority for the details for that national id number.
If my customer db is leaked it's considered "bad" but it's not disastrous. All those addresses/names/ids were mostly public anyway (there could be protected identities etc so one shouldn't assume all is public)
- cm2187 9y agoYou call it public, I call it universal. We are talking about the same thing.
- alkonaut 9y agoRight: universal (everyone has one) and merely an id, not a secret used for verification. An important thing is to keep a 2fa tied to each id. An address works, because then mail can be used as 2fa.