(no title)
sleevi | 4 years ago
That is, it specifically targets websites (particularly Very Large Online Platforms) that they MUST accept such ID in lieu of an email or password, at the user’s request. This was part of the original motivation for the revisions, to target “Sign in with Facebook” or “Sign in with Google” and require such sites also offer a “Login with EU” option.
Source: https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=COM%3A20...
denton-scratch|4 years ago
That means there is nothing preventing $TSP from forging my certificate, and giving it to criminals/government-agents, and nothing to keep the TSP in line, because the single audit constraint is "Keep the Minister satisfied".
I personally don't have a problem with the idea of replacing passwords with user-certs, provided I get to generate my own cert with my own private key. But the evidence is that general users can't learn how to use certificates.
I hate passwords, but I'd rather use passwords than a user-cert issued by an unreliable CA.
Jensson|4 years ago
Aerroon|4 years ago
sleevi|4 years ago
Source: https://www.enisa.europa.eu/publications/qualified-website-a...
Jensson|4 years ago