DEV Community

Johan Bové
Johan Bové

Posted on • Originally published at social.johanbove.info on

Using Keybase GPG to sign git commits and tags

#git #keybase #pgp

With the Keybase application installed on the "Windows Subsystem for Linux" command line, export the pgp Keybase key and import it into the local gpg keychain:

$ gpg --list-secret-keys --keyid-format LONG
$ keybase pgp pull johanbove
$ git config --global user.signingkey B6A8D5E8
$ keybase pgp export -q 4AAE11D0B6A8D5E8 | gpg --import
$ keybase pgp export -q 4AAE11D0B6A8D5E8 --secret | gpg --allow-secret-key-import --import
$ echo "test" | gpg --clearsign
Enter fullscreen mode Exit fullscreen mode

I also had to add this code into the ~/.bashrc file to make the gpg passphrase prompt work in WSL:

# enable passphrase prompt for gpg
export GPG_TTY=$(tty)
Enter fullscreen mode Exit fullscreen mode

Setting the trust level of the imported key:

$ gpg --list-keys
$ gpg --edit-key E44E71105E920276ED1693294AAE11D0B6A8D5E8
Enter fullscreen mode Exit fullscreen mode

Following the instructions in gpg.

Signing a git tag:

$ git tag -s v1.0.0 -m "Release v1.0.0 signed"
Enter fullscreen mode Exit fullscreen mode

Verifying the git tag:

$ git tag -v v1.0.0
Enter fullscreen mode Exit fullscreen mode

Sources:

Top comments (0)

Read next

foxinfotech profile image

Create Professional Banners with the As Seen On Image Generator Online

Vinish Kapoor -

aaronblondeau profile image

Geospatial Indexing Sampler

aaronblondeau -

pansychurch6 profile image

Software Development and THAT Outsourcing: Essential Insights

Levesque Ford -

swiftproxy_residential profile image

The Critical Role of ISP Whitelist in Strengthening Network Security

Swiftproxy - Residential Proxies -