-
Will the Solo V2 have Challenge-Response authentication for use cases like a second factor for KeePassXC or LUKS? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 11 replies
-
We still think the way to do this is to use the If the question is whether we will implement Yubico's proprietary app (in essence, HMAC-SHA1 challenge-response), the answer is no, we do not plan to do so. This sentiment is shared by other vendors such as Trezor - if OSS such as KeePassXC and LUKS moves on to an actual standard instead of one company's private sauce, everyone wins. For LUKS, I know of https://github.com/shimunn/fido2luks, for password managers (also Bitwarden), I think there are better ways to use a key as second or primary factor to unlock than either of these challenge-reponse approaches. (Since I personally use Bitwarden, if upstream does not implement something, I know I will try once the dust settles). |
Beta Was this translation helpful? Give feedback.
We still think the way to do this is to use the
hmac-secret
extension that is part of the actual standard (it is in essence HMAC-SHA256 challenge-response). In that sense, the answer is, yes, at launch (and Solo V1 has it too, just like every fully certified FIDO2 dongle).If the question is whether we will implement Yubico's proprietary app (in essence, HMAC-SHA1 challenge-response), the answer is no, we do not plan to do so. This sentiment is shared by other vendors such as Trezor - if OSS such as KeePassXC and LUKS moves on to an actual standard instead of one company's private sauce, everyone wins.
For LUKS, I know of https://github.com/shimunn/fido2luks, for password managers (also B…