Skip to content

Latest commit

 

History

History
154 lines (104 loc) · 5.11 KB

gpg-keys.md

File metadata and controls

154 lines (104 loc) · 5.11 KB
Raw
description
This page describes setting up identification details which can be used to verify code was written by you or software was released by you. GPG keys are used to sign code commits or code releases

Use GPG keys

Generating a new key

Generating a new key with Ubuntu

# on 18.04
gpg --full-gen-key;

# on 16.04/macOS
gpg --gen-key;

You will be asked for your name and email address. Note that the email address will be public, so use a masked email which both Github (can be found here) and Gitlab (can be found in the Commit email sub-section here) provides.

Listing existing keys

gpg --list-secret-keys --keyid-format LONG

Exporting the GPG key

Use cases: 1. Adding GPG keys to platforms

List the keys and get the key id

gpg --list-secret-keys --keyid-format LONG
# example output:
#   ...
#   sec   4096R/C4CC3911D49AB2D8 2020-01-07 [expires: 2021-01-07]
#               ^^^^^^^^^^^^^^^^
#               \-> the key id

Export the pbulic key

# copy and paste the key id from above to generate the public key
gpg --armor --export C4CC3911D49AB2D8
# example output:
# -----BEGIN PGP PUBLIC KEY BLOCK-----
# ...
# -----END PGP PUBLIC KEY BLOCK-----

Adding GPG keys to platforms

Adding GPG keys to Gitlab

Login to Gitlab and visit https://gitlab.com/profile/gpg_keys. Run the steps in Exporting public key and paste the exported public key block in.

Adding GPG keys to Github

Login to Github and visit https://github.com/settings/keys. Run the steps in Exporting public key and paste the exported public key block in.

Using GPG keys in Git

Using a key on a per-repo basis

This method assumes that you would like to sign commits for only one repository

Step 1. The local Git configuration for a repository should be at .git/config, open it up and add:

[user]
  name = your name
  email = [email protected]
  signingkey = XXXXXXXXXXXXXXXX

Replace the signingkey value with the desired key ID from the output of the List the keys and get the key id section.

You're done.

Using one key to rule them all

This method assumes that you'd only like to generate one key and use them to sign ALL commits.

Step 1. Find the root .gitconfig by running:

git config --global --list --show-origin

The root .gitconfig is typically at ${HOME}/.gitconfig

Step 2. In the .gitconfig, add the following:

[user]
  name = your name
  email = [email protected]
  signingkey = XXXXXXXXXXXXXXXX

Replace the signingkey value with the desired key ID from the output of the List the keys and get the key id section.

Using the includeIf directive

This method assumes you have a local directory structure that mimics the SCM platform you're using. For example, a repository at https://github.com/zephinzer/wiki.joeir.net should be located at ${HOME}/github.com/zephinzer/wiki.joeir.net or ${HOME}/code/github.com/zephinzer/wiki.joeir.net

Step 1. Find the root .gitconfig by running:

git config --global --list --show-origin

The root .gitconfig is typically at ${HOME}/.gitconfig

Step 2. In the root .gitconfig, add the directive:

[includeIf "gitdir:**/github.com/"]
  path = ~/.github.com.gitconfig

Step 3. Then create the file at ~/.github.com.gitconfig with the following content:

[user]
  name = your name
  email = [email protected]
  signingkey = XXXXXXXXXXXXXXXX

Replace the signingkey value with the desired key ID from the output of the List the keys and get the key id section.

Step 4. Repeat steps 2-3 for as many SCM platforms as you are using

Note that if you, like me commit your dotfiles to a public repository for others to copy/paste as needed, it might be useful to use the include directive to include a path that isn't committed to your dotfiles such as:

[include]
  path = ~/.gitconfig.d

You can chain other includeIf directives from your ~/.gitconfig.d file as needed to SCM platforms whose URLs are better left out of the public eye.

Other Resources