#2258 Exclude KeepassXC from proven packagers access
Closed: Invalid by germano. Opened by germano.

In a world where there is activity of nation state sponsored hackers, password managers are a fundamental asset for personal security.
I am actively maintaining KeepassXC package since it was created, and at every update I do enforce security best practices to be sure that the new package source has not been altered (verification of GPG signature, SHA512, contacting upstream developers).
Today KeepassXC 2.5.0 has been submitted to Fedora repositories by a proven packager without prior notice as it is stated in policy for proven packagers
====
Provenpackagers should try to communicate with owners of a package in bugzilla, irc or email prior to making changes
https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/
====
It has even been pushed to F32 and F31 stable repository (due autokarma), so I had to stop the auto push process to be able to have the time to verify things like the GPG signature of the package and the SHA512.
2.5.0 has been released upstream 3 days ago, and the previous 2.4.3 version had not any kind of important bug, so there is no need to push a 2.5.0 without alerting the package maintainers. Moreover I was already taking care of it, and let me stress that I have never ever been unresponsive.
So I am asking FESCO to revoke proven packagers access to KeepassXC


Have you tried to talk to the provenpackager?

Agree with @churchyard. Prior filing this ticket you really need to contact @limb personally and ask for the reasons.

I agree it might be not nice from Gwyn, however remember that the package is not "yours".

My apologies; I use keepassxc and was alerted to the upgrade. My intention was to assist, not to disrupt. I wasn't aware that you did additional verification for updates, keep in mind that I may also have done so. If you'd like to ensure this, I would recommend either incorporating these verifications into the RPM build process, or documenting them in detail (or a script) in comments in the spec near the Version and Release tags to catch other packagers' attention.

I decided to abort this request, since I better enforce automated signatures check as I planned time ago https://bugzilla.redhat.com/show_bug.cgi?id=1514247 rather than blocking access from proven packagers.
But please read my following comments to your messages

ignatenkobrain:
Prior filing this ticket you really need to contact @limb personally and ask for the reasons.

The problem is not strictly related to limb, the problem is the general attitude of proven packagers (more details below).

ignatenkobrain:
however remember that the package is not "yours".

I would like to stress that even if the package is obviously not mine, I had to interrupt my real life activities to urgently stop the new update from being sent to stable repository due autokarma, because I needed to verify signatures and karma feedbacks from users. Moreover user feedbacks plus a quick view on Github issues page, suggested that the 2.5.0 release should be skipped because of some new bugs despite having received positive karma feedbacks.
Many times it happens that a proven packager edited something without contacting the package maintainer and not even checking if the change has broken something, so I had to intervene to put things in order. Well then I do demand respect for my time, in particular because I always timely do maintain packages when needed and I do care about providing the best user experience, that is what makes Fedora one of the best Linux distributions.

limb:
My apologies; I use keepassxc and was alerted to the upgrade. My intention was to assist, not to disrupt.

Nothing personal against you limb, I know your commitment to the Fedora Project and longtime volunteership

limb:
If you'd like to ensure this, I would recommend either incorporating these verifications into the RPM build process, or documenting them in detail (or a script) in comments in the spec near the Version and Release tags to catch other packagers' attention.

Yes I already planned to do it (https://bugzilla.redhat.com/show_bug.cgi?id=1514247) but I had no time yet to do it. I will do it when I will have some spare time, anyways feel free to contribute.

Have a nice day

Metadata Update from @germano:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

Metadata