2 ms·

Manually enrolling multiple devices/apps is pretty much the main thing that I view as impractical (especially because I need a system that can handle a range of

Manually enrolling multiple devices/apps is pretty much the main thing that I view as impractical (especially because I need a system that can handle a range of authentication options: not everything supports passkeys, some passkey implementations prevent enrolling multiple devices, and that's the standard for TOTP as well). I have a lot of accounts, and it's really not something I can manage reliably to make sure that two different systems are in sync. The thing is, this seems like an entirely solvable problem, from multiple angles: e.g. an end-to-end encrypted sync between devices (using some pairing process), or, even better, a way to enroll a non-present device as an alternative (though this has some of its own challenges, if not just using a persistent certificate). It suprises me a little that there's nothing that really attempts to address this.

tzs 1y ago
> The thing is, this seems like an entirely solvable problem, from multiple angles: e.g. an end-to-end encrypted sync between devices (using some pairing process), or, even better, a way to enroll a non-present device as an alternative (though this has some of its own challenges, if not just using a persistent certificate). It suprises me a little that there's nothing that really attempts to address this Apple is adding that in iOS 26 and MacOS 26 [1], based on the FIDO specification for this [2]. Google is also in the midst of implementing it [3]. [1] https://fidoalliance.org/9to5mac-apple-work-passkey-portability-is-finally-here-in-ios-26-and-macos-tahoe-26/ https://fidoalliance.org/9to5mac-apple-work-passkey-portabil... [2] https://fidoalliance.org/specifications-credential-exchange-specifications/ https://fidoalliance.org/specifications-credential-exchange-... [3] https://fidoalliance.org/mobileidworld-google-developing-passkey-transfer-feature-for-android-password-manager/ https://fidoalliance.org/mobileidworld-google-developing-pas...

tzs 1y ago

> The thing is, this seems like an entirely solvable problem, from multiple angles: e.g. an end-to-end encrypted sync between devices (using some pairing process), or, even better, a way to enroll a non-present device as an alternative (though this has some of its own challenges, if not just using a persistent certificate). It suprises me a little that there's nothing that really attempts to address this Apple is adding that in iOS 26 and MacOS 26 [1], based on the FIDO specification for this [2]. Google is also in the midst of implementing it [3]. [1] https://fidoalliance.org/9to5mac-apple-work-passkey-portability-is-finally-here-in-ios-26-and-macos-tahoe-26/ https://fidoalliance.org/9to5mac-apple-work-passkey-portabil... [2] https://fidoalliance.org/specifications-credential-exchange-specifications/ https://fidoalliance.org/specifications-credential-exchange-... [3] https://fidoalliance.org/mobileidworld-google-developing-passkey-transfer-feature-for-android-password-manager/ https://fidoalliance.org/mobileidworld-google-developing-pas...