From ba2f74b0e4b0c0e9d0acbf7d4be364cbbdc68597 Mon Sep 17 00:00:00 2001
From: Rich Wareham <rjw57@cam.ac.uk>
Date: Mon, 8 Nov 2021 13:11:53 +0000
Subject: [PATCH] add note on updating public key ring
---
docs/contact/public-keys.md | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/docs/contact/public-keys.md b/docs/contact/public-keys.md
index 9fa1683b..116b2bb7 100644
--- a/docs/contact/public-keys.md
+++ b/docs/contact/public-keys.md
@@ -79,6 +79,21 @@ gpg --no-default-keyring --keyring ./teampubkeys.gpg --armour \
The use of `--no-default-keyring` helps ensure that the key you use for a
recipient is one from our team keyring and not a personal key.
+## Updating the public key ring
+
+If you're a DevOps division member, you can open a merge request on the
+[guidebook
+project](https://gitlab.developers.cam.ac.uk/uis/devops/docs/guidebook/) in
+GitLab updating `docs/downloads/teampubkeys.gpg`. To import your _public_ key
+into the keyring:
+
+```sh
+gpg --no-default-keyring --keyring ./teampubkeys.gpg --import [KEYFILE]
+```
+
+where `[KEYFILE]` is your public key. The GPG manual has [a page on extracting
+your public key](https://www.gnupg.org/gph/en/manual/x56.html).
+
<!--
We vendor our own OpenPGP.js copy to ensure we know the precise version.
-->
--
GitLab