rixxc/KeePassDX
1
0
Fork 0
mirror of https://github.com/Kunzisoft/KeePassDX.git synced 2025-12-04 15:49:33 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add Autofill section and warning 2 databases

Jérémy JAMET
2022-03-17 10:19:40 +01:00
parent 89e4501b75
commit ef85070647
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
OTP.md

@@ -5,6 +5,10 @@ KeePassDX is compatible with the algorithms:
* **HMAC-based one-time password (HOTP)**. Algorithm that generates a single token from a secret key and a counter. - standard [RFC 4226](https://tools.ietf.org/html/rfc4226) * **HMAC-based one-time password (HOTP)**. Algorithm that generates a single token from a secret key and a counter. - standard [RFC 4226](https://tools.ietf.org/html/rfc4226)
* **Time-based one-time password (TOTP)**. Algorithm that generates a token every x secondes from a secret key depending on the current time. - Standard [RFC 6238](https://tools.ietf.org/html/rfc6238) and steam. * **Time-based one-time password (TOTP)**. Algorithm that generates a token every x secondes from a secret key depending on the current time. - Standard [RFC 6238](https://tools.ietf.org/html/rfc6238) and steam.
**It is strongly recommended to create a separate database for OTP credentials: if passwords and OTP credentials are stored in the same place, there is no longer any point in using a second identification factor.**
_To compare, it's like putting two locks on the same door and putting the two keys on the same key ring, it makes it more complex but there is no gain in security. You might as well make one lock a little more secure._
# 2FA Token Generator # 2FA Token Generator
Thanks to the TOTP generation function, **it is possible to use theKeePassDX app as a token generator for external services using two-factor authentication (2FA)**. Thanks to the TOTP generation function, **it is possible to use theKeePassDX app as a token generator for external services using two-factor authentication (2FA)**.
@@ -41,3 +45,8 @@ KeePassDX uses the links generated by the QR codes to save new OTP keys.
To do this, just share the link from your favorite [code reader](https://github.com/dmitriy-ilchenko/QrAndBarcodeScanner) app. To do this, just share the link from your favorite [code reader](https://github.com/dmitriy-ilchenko/QrAndBarcodeScanner) app.
You can also extract the parameters (secret key, algorithm, period, digits) manually from the otpauth link and copy it into the fields provided. If some parameters are not indicated, simply leave those of the default form. You can also extract the parameters (secret key, algorithm, period, digits) manually from the otpauth link and copy it into the fields provided. If some parameters are not indicated, simply leave those of the default form.
## Autofill
The autofill of OTP tokens is very complicated and cannot be generalized because most forms do not use a standardized format and different metadata, so it is not possible to identify the fields to be filled in.
To overcome this problem, the most efficient solution is to copy the OTP token directly from the list of entries in KeePassDX (make sure the `Settings - Appearance - Show OTP Token` is activated)
Associated issue: https://github.com/Kunzisoft/KeePassDX/issues/553#issuecomment-912936390