There is still an /srv/git/.ssh/authorized_keys file on pagure01.fedoraproject.org from when we were using Gitolite (before the Pagure keyhelper script was put in action). This file is used as a last resort by SSH if the keyhelper can't find the key in its database. As a consequence, this means that any keys that were in the Gitolite era and then removed from Pagure, are not accepted by the Keyhelper, but by Gitolite. Which means that people who removed a key after the Gitolite era, but no are trying to use that key, connect to Gitolite instead.
/srv/git/.ssh/authorized_keys
pagure01.fedoraproject.org
This does not constitute a security issue for the access checks because the correct update hook is in place, which means Pagure's checks are enforced. It may be a problem if a user had a key in Gitolite-era that got compromised, which would still be active now.
update
I hit this problem because I was trying to access a project created post-Gitolite-era, with a key from Gitolite-era, which meant Gitolite told me I don't have permissions to write.
This is probably very confusing to users (it was very confusing to me!), so maybe the authorized_keys file can be removed?
authorized_keys
I've renamed the file so the issue doesn't happen anymore, but this will get nicely cleaned up anyway when we rebuild this host to RHEL8 post colo-move
Closing this ticket as the work is done.
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)