Any GitHub user account can contain GPG keys used for signed commits.
To verify these signatures, your local gpg.program
needs the public key.
To fetch them, just use a URL such as this:
https://github.com/<ACCOUNT>.gpg
When you use the website editor to create commits, those are signed with a key GitHub has instead of a key that the user should be keeping private.
You can retrieve that key from the GPG key servers with:
gpg2 --recv-keys B5690EEEBB952194
Afterwards, you can display that key's information.
$ gpg2 -k 'GitHub <[email protected]>'
pub rsa4096 2024-01-16 [SC]
968479A1AFF927E37D1A566BB5690EEEBB952194
uid [ unknown] GitHub <[email protected]>
The symptoms were:
$ gpg2 -k
gpg: Note: database_open XXXXXXXXX waiting for lock (held by PID) ...
gpg: Note: database_open XXXXXXXXX waiting for lock (held by PID) ...
gpg: Note: database_open XXXXXXXXX waiting for lock (held by PID) ...
gpg: Note: database_open XXXXXXXXX waiting for lock (held by PID) ...
gpg: Note: database_open XXXXXXXXX waiting for lock (held by PID) ...
gpg: keydb_search_first failed: Connection timed out
$