mirror of
https://github.com/keepassxreboot/keepassxc.git
synced 2024-09-20 08:05:40 +00:00
e3c7b570ae
* Remove mention of no longer used IRC network Channels exist on matrix, and on libera.chat now. * Correctly match only files with .png extension The current search would match files such as 'createpng'. * Fix comparison in script The result was always false, due to comparing a literal string instead of a variable. * Use correct license files from upstream Correct license files obtained from: https://www.gnu.org/licenses/old-licenses/gpl-2.0.txt https://www.gnu.org/licenses/gpl-3.0.txt https://www.gnu.org/licenses/old-licenses/lgpl-2.1.txt https://www.gnu.org/licenses/lgpl-3.0.txt * Refresh several shell scripts This fixes several shellcheck warnings, as well as makes the code more robust and have consistent codestyle between all the files. * Trim excess whitespace
21 lines
820 B
Markdown
21 lines
820 B
Markdown
# keepassxc-cr-recovery
|
|
|
|
A small tool that helps you regain access to your KeePassXC password database in case you have it protected with YubiKey challenge-response and lost your key.
|
|
Currently supports KDBX4 databases with Argon2 hashing.
|
|
|
|
## Building
|
|
|
|
Tested with Go 1.13. Just run `go build`.
|
|
|
|
## Usage
|
|
|
|
What you need:
|
|
* your KeePassXC database
|
|
* your challenge-response secret. This cannot be retrieved from the YubiKey, it needs to be saved upon initial configuration of the key.
|
|
|
|
Then just run
|
|
```shell
|
|
keepass-cr-recovery path-to-your-password-database path-of-the-new-keyfile
|
|
```
|
|
It will prompt for the challenge-response secret. You will get a keyfile at the specified destination path. Then, to unlock your database in KeePassXC, you need to check "key file" instead of "challenge response" and load the file.
|