Skip to content

Commit 1b6bb47

Browse files
committed
docs: key from keyserver, check key before import to production
1 parent 3356e98 commit 1b6bb47

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

doc/admin_guide.txt

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1935,9 +1935,28 @@ and import it using::
19351935

19361936
gpg --homedir /path/to/tracker/gpg --import user-public-key.asc
19371937

1938+
You may also be able to get it from a public keyserver using::
1939+
1940+
gpg --recv-keys KEYID
1941+
1942+
where the ``KEYID`` is supplied by the roundup user.
1943+
19381944
While Roundup supports multiple addresses for each user, only the
19391945
primary address supports PGP signed or encrypted messages.
19401946

1947+
You should verify that the public key is sane and has few signatures
1948+
attached. You can import a key into a throw away keystore::
1949+
1950+
mkdir throwaway
1951+
gpg --homedir throwaway -- import user-public-key.asc
1952+
gpg --homedir throwaway --list-sigs
1953+
1954+
and verify that the number of sig lines is small (under 10 or so). If
1955+
it takes a long time to import you can kill the import without
1956+
affecting your production keystore. Large numbers of sig lines can
1957+
take a long time to import/access when compressed. See:
1958+
https://nvd.nist.gov/vuln/detail/CVE-2022-3219.
1959+
19411960
.. comment:
19421961
Questions:
19431962

0 commit comments

Comments
 (0)