|
2 | 2 | :description: |
3 | 3 | Documentation on how to report security issues with |
4 | 4 | Roundup. Also index to security related portions in other |
5 | | - Roundup documentation. |
| 5 | + Roundup documentation. How to verify distribution using gpg. |
6 | 6 |
|
7 | 7 | .. index:: |
8 | 8 | single: Reporting Security Issues |
9 | 9 | single: Security Issues, Reporting |
10 | 10 |
|
11 | 11 |
|
12 | | -====================================== |
13 | | -Reporting Security Issues with Roundup |
14 | | -====================================== |
| 12 | +======================= |
| 13 | +Roundup Security Issues |
| 14 | +======================= |
15 | 15 |
|
16 | 16 | Security issues with Roundup should be reported by email to: |
17 | 17 |
|
18 | 18 | [email protected] (John Rouillard) |
19 | 19 |
|
20 | 20 | [email protected] (Ralf Schlatterbeck) |
21 | 21 |
|
22 | | -Also you can find rouilj on irc in channel #roundup at irc.oftc.net (see |
23 | | -Contact_ for more directions and web interface). |
24 | | - |
25 | | -Use these mechanisms to establish initial contact. |
| 22 | +If these fail, you can find rouilj on irc in channel #roundup at |
| 23 | +irc.oftc.net (see Contact_ for more directions and web |
| 24 | +interface). Methods listed at Contact_ are all public, so they should |
| 25 | +be used to contact somebody with the Roundup project for establishing |
| 26 | +a proper method of reporting the security issue. |
26 | 27 |
|
27 | 28 | .. _Contact: https://www.roundup-tracker.org/contact.html |
| 29 | + |
| 30 | +Verify Source Tarball |
| 31 | +--------------------- |
| 32 | + |
| 33 | +.. index:: |
| 34 | + single: Distribution, verify with gpg |
| 35 | + single: Signature, verify |
| 36 | + |
| 37 | +If you download the source tarball using ``python3 -m pip download |
| 38 | +roundup`` or from https://pypi.org/project/roundup/#files you can |
| 39 | +verify the file using gpg. |
| 40 | + |
| 41 | +This is the information on the public PGP/GPG key used to sign Roundup |
| 42 | +distributions. It is used to sign the 1.6.0, 2.2.0, and newer |
| 43 | +releases. (Note that the @ sign in email addresses have been replaced |
| 44 | +with the word "at" to reduce spam directed at the mailing list.):: |
| 45 | + |
| 46 | + Key info: Roundup Team (signing key for roundup releases) |
| 47 | + <roundup-devel at lists.sourceforge.net> |
| 48 | + Expires: 2028-07-17 |
| 49 | + Key fingerprint = 411E 354B 5D1A F261 25D6 2122 1F2D D0CB 756A 76D8 |
| 50 | + |
| 51 | +Releases 1.6.1, 2.0.0 and 2.1.0 were accidentally signed with this key |
| 52 | +[1]_:: |
| 53 | + |
| 54 | + Key info: John Rouillard (Roundup Release Key) |
| 55 | + <rouilj+roundup at ieee.org> |
| 56 | + Expires: 2023-07-09 |
| 57 | + Key fingerprint = A1E6 364E 9429 E9D8 2B3B 2373 DB05 ADC4 2330 5876 |
| 58 | + |
| 59 | +.. [1] Use gpg to import this key from the keyserver pgp.mit.edu |
| 60 | + if you need to verify one of these releases. Use the gpg |
| 61 | + pgp.mit.edu keyserver example replacing the key fingerprint |
| 62 | + with the one starting A1E6. |
| 63 | + |
| 64 | +You can import a key from pgp.mit.edu using:: |
| 65 | + |
| 66 | + gpg --keyserver pgp.mit.edu --receive-keys 411E354B5D1AF26125D621221F2DD0CB756A76D8 |
| 67 | + |
| 68 | +where the fingerprint (without spaces) is used to identify which key |
| 69 | +to receive. You can also extract and import the file |
| 70 | +``tools/roundup.public.pgp.key`` from the download source tarball |
| 71 | +using:: |
| 72 | + |
| 73 | + tar -xzvf roundup-2.2.0.tar.gz -O \ |
| 74 | + roundup-2.2.0/tools/roundup.public.pgp.key > pub.key |
| 75 | + |
| 76 | + gpg --import pub.key |
| 77 | + |
| 78 | +Once you have loaded the public key, you need a detached signature for |
| 79 | +your release. PyPI used to support uploading gpg detached |
| 80 | +signatures. However that is no longer supported and downloading |
| 81 | +existing signatures may not work in the future. |
| 82 | + |
| 83 | +As a result, the signatures for all Roundup final releases starting |
| 84 | +with 1.6.0 have been moved and are linked below: |
| 85 | + |
| 86 | +* `2.2.0 <../signatures/roundup-2.2.0.tar.gz.asc>`_ |
| 87 | +* `2.1.0 <../signatures/roundup-2.1.0.tar.gz.asc>`_ |
| 88 | +* `2.0.0 <../signatures/roundup-2.0.0.tar.gz.asc>`_ |
| 89 | +* `1.6.1 <../signatures/roundup-1.6.1.tar.gz.asc>`_ |
| 90 | +* `1.6.0 <../signatures/roundup-1.6.0.tar.gz.asc>`_ |
| 91 | + |
| 92 | +To use it, download the correct versioned link and verify it with |
| 93 | +(note 1.5.7 is a dummy version, use the correct version number):: |
| 94 | + |
| 95 | + gpg --verify roundup-1.5.7.tar.gz.asc roundup-1.5.7.tar.gz |
| 96 | + |
| 97 | +You should see:: |
| 98 | + |
| 99 | + gpg: Signature made Wed 13 Jul 2022 12:24:14 AM EDT |
| 100 | + gpg: using RSA key 411E354B5D1AF26125D621221F2DD0CB756A76D8 |
| 101 | + gpg: Good signature from "Roundup Team (signing key for roundup releases) <roundup-devel at lists.sourceforge.net>" [unknown] |
| 102 | + gpg: WARNING: This key is not certified with a trusted signature! |
| 103 | + gpg: There is no indication that the signature belongs to the owner. |
| 104 | + Primary key fingerprint: 411E 354B 5D1A F261 25D6 2122 1F2D D0CB 756A 76D8 |
| 105 | + |
| 106 | +which verifies the tarball integrity. The WARNING is expected and the |
| 107 | +date corresponds to the newest renewal of the Roundup key. As long as |
| 108 | +you see the output starting with "Good signature from" followed by the |
| 109 | +Key Info for your key, everything is OK. |
| 110 | + |
| 111 | +If something is wrong you will see: |
| 112 | + |
| 113 | + gpg: Signature made Wed 13 Jul 2022 12:24:14 AM EDT |
| 114 | + gpg: using RSA key 411E354B5D1AF26125D621221F2DD0CB756A76D8 |
| 115 | + gpg: BAD signature from "Roundup Team (signing key for roundup releases) <roundup-devel at lists.sourceforge.net>" |
| 116 | + |
| 117 | +*do not use* the tarball if the signature is BAD. Email the |
| 118 | +roundup-devel mailing list if you have this happen to you. |
0 commit comments