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 QR code configuration

Jérémy JAMET
2022-03-17 10:58:06 +01:00
parent ed8fb3ff4e
commit 4a505389c2
1 changed files with 22 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
OTP.md

@@ -22,27 +22,39 @@ The secret key is an important element! This is sensitive data that allows you t
For example, if you have a two-factor Google authentication, it is recommended to have two KeePass databases. In the first, your Google password, and in the second, the secret key that generates the TOTP token. For example, if you have a two-factor Google authentication, it is recommended to have two KeePass databases. In the first, your Google password, and in the second, the secret key that generates the TOTP token.
## HOTP ## QR Code
KeePassDX can use the links generated by QR codes to register new OTP keys. But KeePassDX does not contain a QR code reader, other apps are dedicated to that and do the job very well.
So you just have to use your favorite code reader app (ie: [QR & Barcode Scanner](https://github.com/dmitriy-ilchenko/QrAndBarcodeScanner)) and share the link to KeePassDX:
1. Open your database in modification
2. Scan your QR code with a compatible app
3. Share the link to KeePassDX (ie: "share as text")
4. KeePassDX switches to "Save" mode
5. Select an entry (the otp field of the entry is automatically filled)
6. Save the entry
7. Voilà! The OTP token is automatically generated
8. Check that your QR code reader app does not have a history, if so, delete the data.
## Manually
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.
### HOTP
[[images/OTP/HOTP_form.jpg]] [[images/OTP/HOTP_form.jpg]]
## TOTP ### TOTP
[[images/OTP/TOTP_RFC6238_form.jpg]] [[images/OTP/TOTP_RFC6238_form.jpg]]
## TOTP Steam ### TOTP Steam
Steam unfortunately does not use the standardized TOTP algorithms, but instead a custom one. Steam unfortunately does not use the standardized TOTP algorithms, but instead a custom one.
**This special algorithm has been implemented in KeePassDX and is configurable in the Pro version!** **This special algorithm has been implemented in KeePassDX and is configurable in the Pro version!**
[[images/OTP/TOTP_Steam_form.jpg]] [[images/OTP/TOTP_Steam_form.jpg]]
## QR Code # Autofill
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.
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. 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) 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 Associated issue: https://github.com/Kunzisoft/KeePassDX/issues/553#issuecomment-912936390