Compared to 2FA implemented in KeeWeb, this is a much better option because secrets cannot be exported from a YubiKey. YubiKey can be used to generate one-time codes for 2FA. ⚠️ It's strongly recommended to save the file manually after making changes to avoid issues mentioned above. ✅ Keepass2Android, the file must be in KDBX4 format.The implementation is compatible to KeePassXC and not KeePass/KeeChallenge (see the list below), which means, you will be able to use it with clients implementing YubiKey integration this way.In case you won't be able to touch the YubiKey in a timely manner, sync will fail. If a file is changed remotely and these changes arrived during sync, you will see the same question again.If you fail to do so in a timely manner or reject the request, syncing or saving will result in an error. This means that if you have automatic save enabled, you will be asked to press the button on your YubiKey. YubiKey must be plugged in and you have to press the key every time a file is saved or synced.To enable it, check the corresponding option in settings.Īfter changing YubiKey settings of a file it's recommended to delete it on other devices and re-add again, to avoid syncing issues. Depending on your threat model it may be unexpected or not desired, so it's disabled by default. It's possible to save YubiKey codes in memory while the app is open. If the YubiKey is not plugged in, you will be prompted about it. Once selected, YubiKey choice is saved in settings, next time it will be used automatically. To select a YubiKey, click the YubiKey icon on the open screen. The implementation is compatible with KeeChallenge plugin for KeePass, KeePassXC, and many other apps.
This mode is used to store a component of master key on a YubiKey. Challenge-response: to provide a hardware-backed component of master key.YubiKey can be used in several modes with KeeWeb:
0 kommentar(er)
