4 ms·
There should be a way to invalidate a token on all services in a single time. Maybe service providers could provide an https endpoint to perform this? It migh
by znpy 8y ago
There should be a way to invalidate a token on all services in a single time.
Maybe service providers could provide an https endpoint to perform this?
It might be a good idea to give a distinct well-known name to this kind of endpoints, and provide such endpoints in the registration email so that when a token is to be invalidated, an user can regexp-search the well-known name of the endpoint in their mailbox, retrieve all such endpoints and invalidate the compromised token against all of them.
- jiveturkey 8y ago> Maybe service providers could provide an https endpoint to perform this? That's a good idea, with one caveat. It needs to be quite hard to revoke a token. Proof of 1-factor is not sufficient; an attacker could then simply revoke your token and then gain access. So a lost token is quite a challenge, even if there is a revoke URL. This doesn't seem automatable (to revoke all "in a single time" as you say). > provide such endpoints in the registration email In addition, the browser should record U2F interactions and know all sites on which a token was registered. Then such a list is very easily accessible, as long as the browser log is available. If it isn't, well you have email as a backup log. The fact that you can't unilaterally revoke all token registrations is the main weakness of U2F. (besides the cost and the user action required for uptake of it)