This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
blug-canary-2 [2020/04/19 12:51] persmule |
blug-canary-2 [2024/01/17 11:44] persmule |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Beijing GNU/Linux User Group Canary (2/3) ====== | ||
- | |||
< | < | ||
-----BEGIN PGP SIGNED MESSAGE----- | -----BEGIN PGP SIGNED MESSAGE----- | ||
Line 8: | Line 6: | ||
==================================== | ==================================== | ||
- | Issued for April 2020. | + | Issued for January 2024. |
Don't just trust the contents of this file blindly! Verify the | Don't just trust the contents of this file blindly! Verify the | ||
Line 18: | Line 16: | ||
* biergaizi: 0x255211B2395A5A3E0E48A0F1FAD3EB05E88E8D6D | * biergaizi: 0x255211B2395A5A3E0E48A0F1FAD3EB05E88E8D6D | ||
* persmule : 0xEDFFE248ECFACDE3C805906804A40D21DBB89B60 | * persmule : 0xEDFFE248ECFACDE3C805906804A40D21DBB89B60 | ||
- | * wnereiz | + | * vimacs |
THREE DOCUMENTS IN TOTAL. | THREE DOCUMENTS IN TOTAL. | ||
Line 63: | Line 61: | ||
10. We plan to publish the next of these canary statements in the first three | 10. We plan to publish the next of these canary statements in the first three | ||
- | weeks of May 2020. Special note should be taken if no new canary is published | + | weeks of February 2024. Special note should be taken if no new canary is published |
by that time or if the list of statements changes without plausible explanation. | by that time or if the list of statements changes without plausible explanation. | ||
+ | |||
+ | 11. Due to the ongoing security issues of OpenPGP keyservers, it makes signature | ||
+ | verification an issue and somewhat a challenge. For completeness, | ||
+ | procedures for canary verification is included here. | ||
Special Announcements | Special Announcements | ||
~~~~~~~~~~~~~~~~~~~~~~~~ | ~~~~~~~~~~~~~~~~~~~~~~~~ | ||
- | 1. Since mid-October, | + | 1. We've found a workaround for importing keys on https:// |
- | expired. A new key, 0xEDFFE248ECFACDE3C805906804A40D21DBB89B60, | + | without User-ID. The instructions for verifying persmule' |
- | created and uploaded to https:// | + | been added. |
- | this keyserver. | + | |
- | 2. The new key will be used by persmule to sign future warrant canary | + | Canary Verification Procedures |
- | documents. You can verify the signature by crosschecking the other two | + | ~~~~~~~~~~~~~~~~~~~~~~~~ |
- | documents signed by biergaizi and wnereiz for consistency. | + | |
- | 3. Due to this key rollover, the October message was not signed by persmule. | + | 1. To verify biergaizi' |
- | This did/does not indicate a security incident, all of the statements above | + | |
- | were valid, and are still valid. | + | |
- | 4. Recent attacks on OpenPGP | + | a. Obtain the public key from any traditional |
- | within the community, as a countermeasure, | + | https:// |
- | not published to the https:// | + | is 0x255211B2395A5A3E0E48A0F1FAD3EB05E88E8D6D. |
- | cryptographic information can be obtained from the keyserver, without any | + | |
- | User-ID. Currently, it's impossible to import | + | |
- | User-ID to a standard GnuPG installation, | + | |
- | for a 3rd-party to verify the canary document signed by persmule. | + | |
- | 5. We are looking for a solution. But for now, we decided that the best | + | b. Use the latest GnuPG in any operating system. |
- | option is starting publishing new canary documents using the new key. | + | |
- | As a temporary measure, you can check the canary documents signed by | + | |
- | biergaizi and wnereiz to decide the validity of the Statements. By signing | + | |
- | their own copies, it indicates that the new key has been verified privately | + | |
- | by them as valid. | + | |
- | 6. This effectively reduced the number of signers to two people. It reduces | + | 2. To verify persmule' |
- | the level of confidence, but currently there is no alternative option yet. | + | |
- | 7. Once the technical problem of OpenPGP public key without User-ID | + | a. Due to the previous attacks on OpenPGP keyservers, persmule has published |
- | resolved, you can check the previous signatures retroactively, and this | + | |
- | would effectively restore the level of confidence. You can archive | + | the standard method, it' |
- | persmule' | + | |
- | ensure no data tampering has occured. | + | below. |
- | 8. Unlike persmule, biergaizi | + | b. Obtain the dummy public key from any traditional OpenPGP Keyserver, |
- | but the Key-IDs have been changed to its full fingerprint format | + | such as https:// |
- | canary document for clarity. | + | fingerprint is 0xEDFFE248ECFACDE3C805906804A40D21DBB89B60. Note that, to |
+ | | ||
+ | website to a file or console and use the command "gpg --import" | ||
+ | technical problem, Using "gpg --recv-key" | ||
+ | work. | ||
- | 9. When new information | + | c. This is a special dummy public key with its User-IDs and subkeys stripped |
- | Announcements" | + | that we specifically created, leaving only a " |
+ | E-mail address, " | ||
+ | allowing the subsequent import of additional subkeys. | ||
+ | |||
+ | d. Next, with the stub key already imported, obtain the public key from | ||
+ | https:// | ||
+ | Because the dummy key with its stub User-ID is already in presence, it's | ||
+ | now possible to import the https:// | ||
+ | |||
+ | e. Use the latest GnuPG in most operating system, | ||
+ | | ||
+ | other systems should work just fine, but not Fedora. The subkeys contains | ||
+ | signatures made with Brainpool curves, which are disabled on Fedora due to | ||
+ | potential patent-licensing problems, causing a "Unknown elliptic curve" | ||
+ | error. | ||
+ | |||
+ | 3. To verify vimacs' | ||
+ | |||
+ | a. Obtain the public key from any traditional OpenPGP Keyserver, such as | ||
+ | https:// | ||
+ | is 0x7079B481F04B5D8B65A0ECDEEA2DB82FE04A9403. | ||
+ | |||
+ | b. Use the latest GnuPG in any operating system. | ||
Proof of Freshness | Proof of Freshness | ||
Line 117: | Line 131: | ||
$ rsstail -1 -n5 -N -u https:// | $ rsstail -1 -n5 -N -u https:// | ||
- | What essential shops are open during the coronavirus lockdown? | + | Post Office scandal latest: Fujitsu data was 'manipulated', inquiry hears - watch live |
- | Watch: Can you get coronavirus twice? | + | Fujitsu boss admits moral obligation to compensate Horizon victims |
- | 'I can't get an online home delivery slot - what should I do?' Coronavirus Q&A | + | |
- | These are the NHS workers who have died from coronavirus | + | |
- | What is coronavirus, how did it start and how big could it get? | + | Police failings left girls at mercy of Rochdale grooming gangs, report finds |
$ rsstail -1 -n5 -N -u https:// | $ rsstail -1 -n5 -N -u https:// | ||
+ | | ||
+ | | ||
+ | Why Rishi Sunaks Conservatives Have Splintered Into Factions | ||
+ | | ||
+ | | ||
$ date -R -u | $ date -R -u | ||
- | Sun, 19 Apr 2020 12:49:15 +0000 | + | Wed, 17 Jan 2024 11:42:14 +0000 |
-----BEGIN PGP SIGNATURE----- | -----BEGIN PGP SIGNATURE----- | ||
- | iQEzBAEBCgAdFiEEwonfPqgFyacM7J3iwYAPuUJ74CEFAl6cSPAACgkQwYAPuUJ7 | + | iQIzBAEBCgAdFiEEDfvrUpjKhXrxhHZrG+3+G67tLh4FAmWnvR4ACgkQG+3+G67t |
- | 4CHIaQf/WgyGPYYA+cx9U129nxuPUi27x1BEVYoTaNsA2gsp732R4uH34s2yqz7V | + | Lh79og/+KHssTtLmwpw79b+2y0DkBZ70aN/ |
- | urWULpNZWYA7+k+kFF5zUOfmbDNjwKFVYV9Fd+UXxTwQUMtbF9cudkohduwD09Im | + | wOFf3AVQMnhXNuvDPZRc1T+A/ |
- | 8XPr2A8nQWbRr3r4nIlyev9rHqRZkld73i1o4IG9BvWhAimAe3X0NY1VBeVoD+Ra | + | 2R9iBfylg90koORZb43hkzw3lJSPIXW49DhKJOaXD7eDzZXoVIEf26HtMvUdco28 |
- | etDipf/xrVHPAjTM8fe6dloIMkTEZLFthOcX269qtSBcPjitHSQzcpGA7IJCL5UR | + | fvYnbnAgd6fm+sNJrFLZ+/ |
- | W1xzjnLy71l5IbhHVRrknNbXKvve5VBUsSztGfh9DlTyvucERFd+kZJJUZw/XWRC | + | LgDtFIiEB7iMD8g4EDTSQG1ApcicsB09jX8JVAtJGg/ |
- | b0bIvNTSxTgdxTxxx1MV/oTNgsqcBg== | + | GphoUPlq7gRj/ |
- | =unrx | + | Zq4WGRLem4PO7knyxf7y4DrY/2IxIcilJDx40dCiU6R3m4jkisTfHBbvPpn9MXt4 |
+ | Sdguy9vw64mtgKVvN8aYJFtEU5ahQlEXE7Emi2/Ixb7G4QSmYQGmab8en8cziUPP | ||
+ | 5x6YKV/tr36BwIXOjDXAhAwt2jZKf1e5cbNTnRGk5bfRFSV/ | ||
+ | 5k9jPA9jG58ge1DhBkdfTbkRPCB9mHPMkDv9wYpZ0awrIs1pHKY91cF+EiyBziq+ | ||
+ | Njsbi7pNOa1HzPuMn/ | ||
+ | =HvaA | ||
-----END PGP SIGNATURE----- | -----END PGP SIGNATURE----- | ||
</ | </ |