3 ms·
In a hardware token, there's generally a single master secret and private keys are derived on the fly for each website you register/log into. So you can use 1 s
by ecesena 7y ago
In a hardware token, there's generally a single master secret and private keys are derived on the fly for each website you register/log into. So you can use 1 single hardware token with an unlimited number of sites (note that you prob want to register at least 2 tokens per site, in case you loose one, but this is a different story).
The standard also define the concept of resident keys (RKs), that you can use for passwordless authentication (typically with a PIN on the token, to avoid theft). In this case of course each key consumes a bit of storage, so the number of sites is limited. For example, a Solo key can currently store 50 resident keys. To the best of my knowledge, apart from demo sites, the only "real" site supporting resident keys is microsoft/outlook.com, so this is currently not a real practical limitation.
- stavros 7y agoCorrection, resident keys are used for usernameless authentication (you don't need resident keys for passwordless). I recently (last week) wrote a Django library for WebAuthn (https://pypi.org/project/django-webauthin/ https://pypi.org/project/django-webauthin/) and use it on a few of my sites (https://www.pastery.net https://www.pastery.net, https://www.eternum.io https://www.eternum.io and https://www.deadmansswitch.net https://www.deadmansswitch.net, if you want to try it out).