You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user works with signed commits (SSH or GPG key) and wants to verify the keys locally, one must retrieve the public key for the commit's author from GitLab's database and add it to the allowed_signers file (or the file pointed by gpg.ssh.allowedSignersFile git config) and/or the GPG local keyring, enabling the signature verification on git log --show-signatures.
For that, we must use User's API endpoint, which is also available in go-gitlab package.
The text was updated successfully, but these errors were encountered:
At first, we can just print enough information for the user and let one deal with adding that public key to the correct place: "allowed_signers" file in case of SSH signature, and GPG keyring for GPG signature, avoiding system differences, eg. gpggpg2gnome-keyring....
When a user works with signed commits (SSH or GPG key) and wants to verify the keys locally, one must retrieve the public key for the commit's author from GitLab's database and add it to the
allowed_signers
file (or the file pointed bygpg.ssh.allowedSignersFile
git config) and/or the GPG local keyring, enabling the signature verification ongit log --show-signatures
.For that, we must use User's API endpoint, which is also available in go-gitlab package.
The text was updated successfully, but these errors were encountered: