comparison doc/admin_guide.txt @ 8485:0fda84bc7584

docs: key from keyserver, check key before import to production
author John Rouillard <rouilj@ieee.org>
date Sun, 07 Dec 2025 17:30:41 -0500
parents ed4ef394d5d6
children 7142740e6547
comparison
equal deleted inserted replaced
8484:3a07e63ec7c7 8485:0fda84bc7584
1933 do this, obtain the user's public key for their primary email address 1933 do this, obtain the user's public key for their primary email address
1934 and import it using:: 1934 and import it using::
1935 1935
1936 gpg --homedir /path/to/tracker/gpg --import user-public-key.asc 1936 gpg --homedir /path/to/tracker/gpg --import user-public-key.asc
1937 1937
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
1938 While Roundup supports multiple addresses for each user, only the 1944 While Roundup supports multiple addresses for each user, only the
1939 primary address supports PGP signed or encrypted messages. 1945 primary address supports PGP signed or encrypted messages.
1946
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.
1940 1959
1941 .. comment: 1960 .. comment:
1942 Questions: 1961 Questions:
1943 1962
1944 Can roundup send signed emails? (looks like no, why??) 1963 Can roundup send signed emails? (looks like no, why??)

Roundup Issue Tracker: http://roundup-tracker.org/