v1.0 Improve OTP handling in various aspects
-
Ask for storage location of OTP secrets
When setting up the first OTP secret in a database, KeePassOTP now asks for the storage location.
You can decide to store the secrets within the respective entries or in a seperate embedded database.
You can switch between these approaches anytime, use KeePassOTP's options to do so. -
Improve KPOTP column
The KPOTP column will now display either the OTP value or only the OTP status (OTP defined / OTP can be defined)
Improves 81cd74f -
Ask for consent to download two factor json file
-
Add option to store recovery codes to OTP setup
These codes can be used to regain access in case OTP generation is no longer possible.
You can now store these codes in KeePassOTP.
Usually a recovery expires after its usage, you need to remove expired codes manually. -
Minor bugfixes
Finally bumped version to 1.0