3 ms·
The point is you would have a different key on different devices, each of which can access your account. This gives you a backup, in fact a better one, because
by rcxdude 3y ago
The point is you would have a different key on different devices, each of which can access your account. This gives you a backup, in fact a better one, because if one is comprimised and locked out you can still use the others. The main challenge is automating this process so you can properly mirror your keyring across multiple devices, which I don't think there's a standard solution to. So it would be a manual process for each account, which kinda sucks.
- j16sdiz 3y ago> The point is you would have a different key on different devices, each of which can access your account. How would you sign up a new service under this scheme? Enroll with one device, swap the hardware key, and enroll with the other key? What if two device are not in the same physical location?
- rcxdude 3y agoAt the moment, yes, that's the process, annoyingly. Ideally, you would sign up with one and then be able to automatically enroll the others, which is in principle possible if you don't use resident keys and instead each device has the public key of the other devices you want enrolled at the same time, but I don't think is currently supported by the standards.
- dathinab 3y agoThere have been many proven approaches how to solve this. For example "blessing" the enrollment of a device using another one, potentially across physical locations (i.e. similar to what discord and steam did at least for a time as far as I remember). > How would you sign up a new service under this scheme? the same way you do now, there is no difference