BLUG Wiki

User Tools

Site Tools

You are here: start » blug-canary-1
Trace:
blug-canary-1

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
blug-canary-1 [2020/04/29 03:48]
BLUG Admin 		blug-canary-1 [2020/05/26 13:47]
BLUG Admin
Line 15: Line 15:
 ==================================== ====================================
  
-Issued for April 2020.+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 25: Line 25:
 * biergaizi: 0x255211B2395A5A3E0E48A0F1FAD3EB05E88E8D6D * biergaizi: 0x255211B2395A5A3E0E48A0F1FAD3EB05E88E8D6D
 * persmule : 0xEDFFE248ECFACDE3C805906804A40D21DBB89B60 * persmule : 0xEDFFE248ECFACDE3C805906804A40D21DBB89B60
-* wnereiz  : 0x0A6A91990AC98712274AA18DFDFF2E13AA25BE72+* vimacs   : 0x7079B481F04B5D8B65A0ECDEEA2DB82FE04A9403
  
 THREE DOCUMENTS IN TOTAL. THREE DOCUMENTS IN TOTAL.
Line 70: Line 70:
  
 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 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 76: Line 76:
 ~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~
  
-1. Since mid-October, persmule's old signing key 0x2987A25DAC8454A5 has +1. Due to personal reasons, wnereiz (0xFDFF2E13AA25BE72) voluntarily decided 
-expired. A new key, 0xEDFFE248ECFACDE3C805906804A40D21DBB89B60, has been +to quit from the warrant canary team and he is no longer a signer of the 
-created and uploaded to https://keys.openpgp.org/, it can be obtained from +warrant canary documents since April 15th, 2020. All statements from the 
-this keyserver.+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. The new key will be used by persmule to sign future warrant canary +2. In the previously mentioned document designed by wneriez in April 2020, 
-documents. You can verify the signature by crosschecking the other two +the date in its statements was mistakenly written as "April 15th, 2019", 
-documents signed by biergaizi and wnereiz for consistency.+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. Due to this key rollover, the October message was not signed by persmule. +3. A new member, vimacs (0xEA2DB82FE04A9403) has became a new signer since this 
-This did/does not indicate a security incident, all of the statements above +month. You can validate the new keys by cross-checking the other two copies of 
-were valid, and are still valid.+this document, signed by biergaizi and persmule.
  
-4. Recent attacks on OpenPGP keyservers have raised great security concerns +4. Due to the ongoing security issues of OpenPGP keyservers, it makes signature 
-within the community, as a countermeasure, persmule's personal User-ID has +verification an issue and somewhat a challenge. For completeness, complete 
-not published to the https://keys.openpgp.org/ keyserver. Instead, only +procedures for canary verification has been added.
-cryptographic information can be obtained from the keyserver, without any +
-User-ID. Currently, it's impossible to import a OpenPGP public key without +
-User-ID to a standard GnuPG installation, as a result, it's not possible +
-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 +Canary Verification Procedures 
-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 +1. To verify biergaizi's signature... 
-their own copies, it indicates that the new key has been verified privately + 
-by them as valid.+    a. Obtain the public key from any traditional OpenPGP Keyserver, such as 
 +    https://keyserver.ubuntu.com, and import the public key. The fingerprint 
 +    is 0x255211B2395A5A3E0E48A0F1FAD3EB05E88E8D6D. 
 + 
 +    b. Use the latest GnuPG in any operating system. 
 + 
 +2. To verify persmule's signature... 
 + 
 +    a. Unfortunately, it's not possible yet. Recent attacks on OpenPGP key- 
 +    servers have raised great security concerns within the community, as a 
 +    countermeasure, persmule's new public key has been published to the 
 +    https://keys.openpgp.org/ keyserver, but without a User-ID. Currently, 
 +    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, and this 
 +    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' signature... 
 + 
 +    a. Due to the recent attacks on OpenPGP keyservers, vimacs has published 
 +    the OpenPGP public key to https://keys.openpgp.org, again, without a User- 
 +    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' old public key from a traditional OpenPGP Keyserver, such 
 +    as https://keyserver.ubuntu.com, and import the public key. The fingerprint 
 +    is 0x7079B481F04B5D8B65A0ECDEEA2DB82FE04A9403. You should see an expired 
 +    public key.
  
-6. This effectively reduced the number of signers to two people. It reduces +    d. Fetch vimacs' new public key from https://keys.openpgp.org, using the same 
-the level of confidence, but currently there is no alternative option yet.+    fingerprint, and import the public key. You should see that the public 
 +    key has been updated.
  
-7. Once the technical problem of OpenPGP public key without User-ID is +    e. Please note that the key is still shown as "expired" because the new key 
-resolved, you can check the previous signatures retroactively, and this +    has no UID associated. But you should be able to see a new, valid (not 
-would effectively restore the level of confidence. You can archive +    expired) subkey by...
-persmule's signature as soon as it's published to your own machine to +
-ensure no data tampering has occured.+
  
-8. Unlike persmule, biergaizi and wnereiz's signing keys are unchanged, +        $ gpg --list-options show-unusable-subkeys      --list-keys 0x7079B481F04B5D8B65A0ECDEEA2DB82FE04A9403
-but the Key-IDs have been changed to its full fingerprint format in the +
-canary document for clarity.+
  
-9. When new information is available, it will be published in the "Special +    f. Now, it's possible to verify the signature by following the standard 
-Announcements" section in future warrant canary documents.+    procedures. Ignore the "key expired" warning (because the latest UID is 
 +    not published, only the expired UIDs are available).
  
 Proof of Freshness Proof of Freshness
Line 124: Line 162:
  
 $ rsstail -1 -n5 -N -u https://www.telegraph.co.uk/news/rss.xml $ rsstail -1 -n5 -N -u https://www.telegraph.co.uk/news/rss.xml
- How does a coronavirus antibody home test kit work, and how do I get one? + Britain in coronavirus lockdown, in pictures 
- These are the NHS workers who have died from coronavirus + Travel restriction updates: Greece could block British arrivals unless UK infection rate falls 
- What is coronavirus, how did it start and how big could it get? + What are the quarantine rules in Spain, France and other countries? 
- When will the UK lockdown next be reviewed? + Watch: How to make a no-sew, government-approved cloth face mask 
- How many coronavirus cases are in your area? Use our tool to find out+ Contact tracing: how will the UK's test, track and trace plan help ease lockdown
  
 $ rsstail -1 -n5 -N -u https://rss.nytimes.com/services/xml/rss/nyt/World.xml $ rsstail -1 -n5 -N -u https://rss.nytimes.com/services/xml/rss/nyt/World.xml
- Spain, France, Greece: Coronavirus World News Live Updates + Coronavirus Live News: Global Updates 
- Coronavirus Diplomacy: How Chinas Red Cross Serves the Communist Party + Heres How Wuhan Tested 6.5 Million for Coronavirus in Days 
- Where Theres a Will in England, Theres a Way + How the Taliban Outlasted a Superpower: Tenacity and Carnage 
- Genoas New Bridge Nears Completion, Turning Tragedy Into Hope + Chinas Military Vows to Defend the Countrys Interests in Hong Kong 
- War Within War: As Saudi Prince Edges Away from Yemen, His Allies Feud+ On a Scottish Isle, Nursing Home Deaths Expose a Covid-19 Scandal
  
 $ date -R -u $ date -R -u
-Wed, 29 Apr 2020 03:46:26 +0000+Tue, 26 May 2020 13:45:10 +0000
  
 -----BEGIN PGP SIGNATURE----- -----BEGIN PGP SIGNATURE-----
  
-iQIzBAEBCgAdFiEEJVIRsjlaWj4OSKDx+tPrBeiOjW0FAl6o+J0ACgkQ+tPrBeiO +iQIzBAEBCgAdFiEEJVIRsjlaWj4OSKDx+tPrBeiOjW0FAl7NHa8ACgkQ+tPrBeiO 
-jW3bhxAAkKYBfvq8Q/lY0iOkWIcZ3haiK0FTjQ7cZ7QB3iOmlrJBtYOMjb58U8Ni +jW2Fkw//f8osAGVE0JRiWjPsUjBpB9lg+CJjpM2KlfY/143Jblg8m8k9CRfWpKhG 
-Q0KVKVsrS7a4OaZHXr7QON9OX03IuAK47g7GF6aRRcVZ3WMLKrMfkqgXS2VZywow +R409J0PiVPmuyGuRhGtPIiZRPeWAiOc+S7DdEhHoF79AI8Pp0w/kfBs4cAOZLi20 
-F5iQjxYZrRd/OX8H82WpTLHdyo7w9XVZz4vjM9bIrx8X/QQSbgFAE54vbuhrhhDJ +HsMhZeEG0BeayfQy3xW6aZrDh0xbQFxG/WW3OBhT4FMkH0nwTn+G6K/KVUS5VWfN 
-u/1ZuJYYYmPbkita9SChMVaJVZcR2FFpxXiM4+jE1LPnh/5moU1r2OY/H7ko3Y6W +ty/jXriSzf22AxGj2r81F0cv9u8JGiTqaHkcfmhT2T5eanRHb87O1+D7Uxj/7IKt 
-gvC36ICo8GLgYgI3l9CxT3wq3efuYSoKe8fiLnky2ZxVqKtfD8qVtG+Cy8aBZWeA +Sz7YSJaht/diPT2T0xTSm2OWorQ4rt0gJ9syqeMduTEXaND5RjnFQdFub7sKIwv2 
-R0aJ2mNdGMbNKqWgEBxKY5zQ3BjV5/yP7ZyELEMmrJ3SGdiZ3UVIDcEBJryxKvix +LOqhWu8AVIlB6HaVmcxl2l+rPIBjEZOv+jvFtAaddrDCRUHWqgx+u55P9fXz0KFu 
-cNfay6nchRu90VZDtQV0TaAd1FD/8dARDTW5WicEm1q36yqiUGM0SagxYybeR86k +uSfiaUmeUbVNXIt9ZIHzo4Er/TvRcbX4FMGYGbntno+A6L0eY2TNIoGj7r40BIyk 
-d3Z9gI1izIKhk4vv8B4g0r5IyrbqNyh02ROioW4KjMMQ59GzOz8wXru1+EKBVPJQ +N6GyLJufnFYFQwKCwo/IIWnDFrycxhb7AxqWxEXbQ+CHeewnsuZZCqnKUIIhtLFd 
-Hjn9O0gjUu1eRfykHjBYqJw/suRwaVRvZIo57A9OypeeENd8bbUZc9mCKHi7DPc5 +byS16qopDsFmTwgrn9EzrNdigRygMlyRA1Tt3nz59O28uqfGSlgBl+eGTA1fAkB2 
-Tc3cdAANelHiSScwd9RFsXnr55I4wzV008vKXj4pGHruSky57l6PK8LxEZMgW6Hu +o3oY87bVmH11XqkFu8NCdbwfvj9DZ1AU+Anq9i1O64nXGI9vc1FN77rrME5PUGUl 
-308WYyX33rMWrukJHr890ENAPPJFr8YMDKztvAeKiJZcpRS+UAM= +yNxgEdwZSXXSfDaVcDtiAOykIYQoEy2n4Pf1PeFMNNWwL/0KqAk= 
-=7ffR+=uqbn
 -----END PGP SIGNATURE----- -----END PGP SIGNATURE-----
 </code> </code>
blug-canary-1.txt · Last modified: 2024/03/30 20:52 by BLUG Admin

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Driven by DokuWiki Template From SyntaxSeed