blug-canary-3
Differences
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-3 [2019/09/15 03:18] Wu Delin |
blug-canary-3 [2020/05/14 12:49] vimacs May 2020 canary #3 |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Beijing GNU/Linux User Group Canary (3/3) ====== | ====== Beijing GNU/Linux User Group Canary (3/3) ====== | ||
| - | < | + | < |
| - | -----BEGIN PGP SIGNED MESSAGE----- | + | |
| Hash: SHA512 | Hash: SHA512 | ||
| Line 8: | Line 7: | ||
| ==================================== | ==================================== | ||
| - | Issued for September 2019. | + | Issued for May 2020. |
| 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 16: | Line 15: | ||
| ~~~~~~~~~~~~~ | ~~~~~~~~~~~~~ | ||
| - | * biergaizi: | + | * biergaizi: |
| - | * persmule : 0x2987A25DAC8454A5 | + | * persmule : 0xEDFFE248ECFACDE3C805906804A40D21DBB89B60 |
| - | * wnereiz | + | * vimacs |
| THREE DOCUMENTS IN TOTAL. | THREE DOCUMENTS IN TOTAL. | ||
| Line 55: | Line 54: | ||
| 8. Our personal safety and security is not threatened. | 8. Our personal safety and security is not threatened. | ||
| - | 9. To avoid security breaches and emphasize the clarity of the warrent | + | 9. To avoid security breaches and emphasize the clarity of the warrant |
| documents, if a signer is temporarily unavailable, | documents, if a signer is temporarily unavailable, | ||
| " | " | ||
| NOT be considered a valid canary document) until the signer becomes available | NOT be considered a valid canary document) until the signer becomes available | ||
| - | again and signs the missed documents. A new signer SHOULD NOT sign a warrent | + | again and signs the missed documents. A new signer SHOULD NOT sign a warrant |
| canary document only due to the temporary unavailability of a existing signer. | canary document only due to the temporary unavailability of a existing signer. | ||
| 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 October 2019. Special note should be taken if no new canary is published | + | weeks of June 2020. 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. | ||
| Line 69: | Line 68: | ||
| ~~~~~~~~~~~~~~~~~~~~~~~~ | ~~~~~~~~~~~~~~~~~~~~~~~~ | ||
| - | None. | + | 1. Due to personal reasons, wnereiz (0xFDFF2E13AA25BE72) voluntarily decided |
| + | to quit from the warrant canary team and he is no longer a signer of the | ||
| + | warrant canary documents since April 15th, 2020. All statements from the | ||
| + | warrant canary documents before this date are still valid. This is an official | ||
| + | decision that can be verified by checking the warrant canary document in April, | ||
| + | signed by wneriez. | ||
| + | |||
| + | 2. In the previously mentioned document designed by wneriez in April 2020, | ||
| + | the date in its statements was mistakenly written as "April 15th, 2019", | ||
| + | which was a typo, but cannot be changed due to the nature of digital signature. | ||
| + | We declare that it's hereby corrected to "April 15th, 2020" | ||
| + | |||
| + | 3. A new member, vimacs (0xEA2DB82FE04A9403) has became a new signer since this | ||
| + | month. You can validate the new keys by cross-checking the other two copies of | ||
| + | this document, signed by biergaizi and persmule. | ||
| + | |||
| + | 4. 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 has been added. | ||
| + | |||
| + | Canary Verification Procedures | ||
| + | ~~~~~~~~~~~~~~~~~~~~~~~~ | ||
| + | |||
| + | 1. To verify biergaizi' | ||
| + | |||
| + | a. Obtain the public key from any traditional OpenPGP Keyserver, such as | ||
| + | https:// | ||
| + | is 0x255211B2395A5A3E0E48A0F1FAD3EB05E88E8D6D. | ||
| + | |||
| + | b. Use the latest GnuPG in any operating system. | ||
| + | |||
| + | 2. To verify persmule' | ||
| + | |||
| + | a. Unfortunately, | ||
| + | servers have raised great security concerns within the community, as a | ||
| + | countermeasure, | ||
| + | https:// | ||
| + | it's impossible to import a OpenPGP public key without User-ID for a | ||
| + | 3rd-party to verify the canary document signed by persmule. | ||
| + | |||
| + | b. We are looking for a solution. But for now, you should check the | ||
| + | canary documents signed by biergaizi and vimacs to decide the validity | ||
| + | of the canary documents. This effectively reduced the number of signers | ||
| + | to two people. It reduces the level of confidence, but currently there is | ||
| + | no alternative option yet. | ||
| + | |||
| + | c. Once the technical problem of using a public key without User-ID is | ||
| + | resolved, you can check the previous signatures retroactively, | ||
| + | would effectively restore the level of confidence. You can archive the | ||
| + | documents to your own machine as soon as it's published to ensure no data | ||
| + | tampering has occurred. | ||
| + | |||
| + | 3. To verify vimacs' | ||
| + | |||
| + | a. Due to the recent attacks on OpenPGP keyservers, vimacs has published | ||
| + | the OpenPGP public key to https:// | ||
| + | ID. But it's possible for a 3rd-party to verify the signatures by following | ||
| + | these steps. | ||
| + | |||
| + | b. Use Debian GNU/Linux operating system and install GnuPG. Other operating | ||
| + | systems may lack the necessary out-of-tree GnuPG patches required, Debian | ||
| + | must be used. | ||
| + | |||
| + | c. Fetch vimacs' | ||
| + | as https:// | ||
| + | is 0x7079B481F04B5D8B65A0ECDEEA2DB82FE04A9403. You should see an expired | ||
| + | public key. | ||
| + | |||
| + | d. Fetch vimacs' | ||
| + | fingerprint, | ||
| + | key has been updated. | ||
| + | |||
| + | e. Please note that the key is still shown as " | ||
| + | has no UID associated. But you should be able to see a new, valid (not | ||
| + | expired) subkey by... | ||
| + | |||
| + | $ gpg --list-options show-unusable-subkeys --list-keys 0x7079B481F04B5D8B65A0ECDEEA2DB82FE04A9403 | ||
| + | |||
| + | f. Now, it's possible to verify the signature by following the standard | ||
| + | procedures. Ignore the "key expired" | ||
| + | not published, only the expired UIDs are available). | ||
| Proof of Freshness | Proof of Freshness | ||
| Line 75: | Line 154: | ||
| $ rsstail -1 -n5 -N -u https:// | $ rsstail -1 -n5 -N -u https:// | ||
| - | NHS bosses tried to ' | + | Travel restriction updates: Antibody tests could allow holidays |
| - | US blames Iran for attack on Saudi Arabia | + | Clap For Our Carers: what time is the NHS applause tonight? |
| - | Girls as young as 11 are filming themselves ' | + | Suicide bomb in eastern Afghanistan kills five |
| - | Sister | + | Exclusive: Second more deadly wave of coronavirus 'to hit Europe this winter' |
| - | 4.8m golden lavatory stolen from Blenheim Palace ... police have nothing | + | Can I take ibuprofen |
| $ rsstail -1 -n5 -N -u https:// | $ rsstail -1 -n5 -N -u https:// | ||
| - | Two Major Saudi Oil Installations Hit by Drone Strike, and U.S. Blames Iran | + | |
| - | Iraq Faces a New Adversary: Crystal Meth | + | |
| - | Top Canadian Intelligence Official Charged With Leaking Secrets | + | |
| - | | + | |
| - | Is Trumps America Tougher on Asylum than Other Western Countries? | + | |
| $ date -R -u | $ date -R -u | ||
| - | Sun, 15 Sep 2019 03:16:48 +0000 | + | Thu, 14 May 2020 12:45:15 +0000 |
| -----BEGIN PGP SIGNATURE----- | -----BEGIN PGP SIGNATURE----- | ||
| - | iQIzBAEBCgAdFiEE3n2KYOSW/ | + | iHUEARYKAB0WIQSk6G5G0KgwQYRNdeEkSefAFKcZwAUCXr09iwAKCRAkSefAFKcZ |
| - | QYSLjRAAhxXRSg6QeZu9yDZl9f2x+RnDTUSobcymkpUEf+8z5taogAkP6AeSaaK8 | + | wGEoAQCgFBMOWin6oU9AFxNJikPxflehBY2hEnmhyop45y39xAEAhIVW595KP0N3 |
| - | JkbLzoOmevMrF675Ljw6tr8xQQsZcz71js8XID1/ | + | c05lwIm4kGUmsrbkgeRAI1nLxOECSwg= |
| - | eRksLM3bs962KgewcJKgcCR6SvnT6bvnKWBJoNaHJyON53vYbWcIYUfZ2zJydwHj | + | =RP5g |
| - | rEIQateXsH9u9q3swKsQV1m/ | + | |
| - | CGdpej3an/ | + | |
| - | gI5tA1Rw51HM87EP5GtPqu3RQclNJLS9JGlIZHb3v+CBpw1yrVUf7J6REmO4ccR2 | + | |
| - | DoEswL0rRqjU7NEJZWasxp1e/ | + | |
| - | 8MLXUwDsU03JAqeEpkjUg0XUHRiaxYRL90yNhvxa+LQ00vfAqm1hCe29CR3DS+Ud | + | |
| - | u1Bt7P61QdUn27CDc4zQU0fUqHsBR+fdqNtEDFTFeuQCIADzmlM1SOdMlxR6r0kP | + | |
| - | S+U0KzJFjv2m7y57J3R+6k/ | + | |
| - | 9broIGU4lmDZeQ+Pu5phU+akqbMcCs7WCQnb3pqFzgC0ZqgbaGM= | + | |
| - | =UdZG | + | |
| -----END PGP SIGNATURE----- | -----END PGP SIGNATURE----- | ||
| + | |||
| </ | </ | ||
blug-canary-3.txt · Last modified: 2024/03/25 01:13 by vimacs
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
