#1069000 secrets: Adding an entry appears to corrupt the database, causing auth to fail on next invocation

Package:
secrets
Source:
secrets
Description:
Manage your passwords
Submitter:
John Darrah
Date:
2024-07-23 06:15:03 UTC
Severity:
normal
#1069000#5
Date:
2024-04-15 02:11:43 UTC
From:
To:
Dear Maintainer,

I added three new entries to the database and then exited
as normal. There was no indication of any issues until I
tried to re-open the database. I entered my pass phrase as
normal and it informed me that the auth had failed. I tried
several more times thinking I mistyped something. I then
selected the "view pass" button to verify that it was
correct, which it was, but it still failed.

I then pulled an old version of the database from backup and
opened it with no issue. I added and entry, saved and
exited, then attempted to re-open but it failed auth again.

I copied a BAD version of the database to a Windows machine
with the latest version of KeepPass installed. It also fails
to auth the pass phrase. From this I must assume that
something is corrupting the file when saving.

#1069000#10
Date:
2024-07-16 09:09:17 UTC
From:
To:
Hi,

From the links below it seems that the issue might have been related to python3-pykeepass and has been fixed in version 4.0.7.

https://gitlab.gnome.org/World/secrets/-/issues/537
https://bugzilla.redhat.com/show_bug.cgi?id=2292507
https://github.com/libkeepass/pykeepass/pull/388

If you can confirm, then this issue can be closed. Latest version of secrets in debian now can be used to test.

#1069000#15
Date:
2024-07-23 06:04:43 UTC
From:
To:
secrets in debian now can be used to test.

Secrets 9.6-1/unstable still fails the same way outlined previously
here. Reverting to the a backup of the .kdbx file allows auth to
complete successfully.