Am 23.11.23 um 14:48 schrieb Sandro:
On 21-11-2023 10:56, Julian Sikorski wrote:
as the CVE (which was not even a problem with keepass in the first place) leading to keepass retirement has been resolved in the meantime, I would like to unretire the package. I have submitted a re-review already:

https://bugzilla.redhat.com/show_bug.cgi?id=2250816

Just a thought in case you aren't aware, KeePassXC [1,2] is still maintained in Fedora and the databases are compatible. So, in case you are after using an existing KeePass database, you can use KeePassXC to do so.

KeePassXC is written in C++ instead of C# and thus does not depend on Mono. There's also a client for mobile called KeePassDX [3].

[1] https://keepassxc.org/
[2] https://src.fedoraproject.org/rpms/keepassxc
[3] https://www.keepassdx.com/

-- Sandro
--

Thanks for the info! I do not remember what the problem was exactly, but last time I tried I ran into issues when trying to use keepassxc cross-platform on Linux, Windows and Android (Keepass2Android) while using Kee for browser integration. Something was missing, so I just kept updating the keepass rpm locally and making sure not to trigger the bug.
With the issue fixed, it makes sense to put keepass back into Fedora.

Best regards,
Julian
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to