Updated Hardware Key (markdown)

Jérémy JAMET
2023-11-13 09:55:54 +01:00
parent eb2c85705a
commit 5c2236c485

@@ -7,9 +7,9 @@ A physical key provides a new means of unlocking that requires physical action b
**_Warning: currently not all hardware key protocols are available in KeePassDX and the implementation is only available in beta for testing._**
There are few types of hardware key protocols used to unlock local database files encrypted with KeePassDX:
- **hmac-secret FIDO2 extension** : Protocol defined by the [FIDO alliance](https://fidoalliance.org/) but not yet standardised for KeePass files. Implemented in almost all physical keys, including [SoloKeys](https://solokeys.com/) which are open source.
- **hmac-secret FIDO2 extension** : Protocol defined by the [FIDO alliance](https://fidoalliance.org/) but not yet standardised for KeePass files. Implemented in almost all physical keys, including [SoloKeys](https://solokeys.com/) which are open source. **Not yet implemented!**
- **HMAC-SHA1 challenge-response** : Protocol defined by [Yubico](https://www.yubico.com/), currently used in the implementation of [KeePassXC](https://keepassxc.org/). This is the recommended way if you have a [Yubikey](https://www.yubico.com/fr/works-with-yubikey/catalog/keepass/).
- **OATH HOTP standard** : Protocol defined in KeePass 2 [OtpKeyProv plugin](https://keepass.info/plugins.html#otpkeyprov). Uses a separate OTP key system that requires an external file that is updated each time the database is changed. Will not be implemented in KeePassDX as it is cumbersome to use.
- **OATH HOTP standard** : Protocol defined in KeePass 2 [OtpKeyProv plugin](https://keepass.info/plugins.html#otpkeyprov). Uses a separate OTP key system that requires an external file that is updated each time the database is changed. **Will not be implemented in KeePassDX as it is cumbersome to use and obsolete**
# SoloKey