Closed J-Jamet closed 3 months ago
The best solution is to save the database with an empty challenge response key, as the write workflow is already running. I've added a toast warning indicating that the action is performed with an empty key.
I've just found a much better way of solving the problem. There was an issue with the outputstream of the save method. It first tested in a temporary file, but opening the outputstream caused a 0byte, so I made a lambda to invoke the outpustream only when no exception was thrown.
Describe the bug
When we save a database with a Yubikey, if the recognition fails, the database is deleted.
KeePass Database
KeePassDX:
Additional context Key Driver 0.1.4