User Tools

Site Tools


blug-canary-3

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
blug-canary-3 [2020/04/30 19:30]
BLUG Admin
blug-canary-3 [2020/05/14 12:49]
vimacs May 2020 canary #3
Line 7: Line 7:
 ==================================== ====================================
  
-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 17: Line 17:
 * biergaizi: 0x255211B2395A5A3E0E48A0F1FAD3EB05E88E8D6D * biergaizi: 0x255211B2395A5A3E0E48A0F1FAD3EB05E88E8D6D
 * persmule : 0xEDFFE248ECFACDE3C805906804A40D21DBB89B60 * persmule : 0xEDFFE248ECFACDE3C805906804A40D21DBB89B60
-wnereiz  0x0A6A91990AC98712274AA18DFDFF2E13AA25BE72+vimacs   0x7079B481F04B5D8B65A0ECDEEA2DB82FE04A9403
  
 THREE DOCUMENTS IN TOTAL. THREE DOCUMENTS IN TOTAL.
Line 62: Line 62:
  
 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 68: Line 68:
 ~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~
  
-1. Due to personal reasons, wnereiz (0xFDFF2E13AA25BE72) voluntarily decided to +1. Due to personal reasons, wnereiz (0xFDFF2E13AA25BE72) voluntarily decided 
-quit from the warrent canary team and he will no longer be a signer of the warrent +to quit from the warrant canary team and he is no longer a signer of the 
-canary documents since April 15th, 2019. All statements from the warrent canary +warrant canary documents since April 15th, 2020. All statements from the 
-documents before this date are still valid. See the Special Announcements of May+warrant canary documents before this date are still valid. This is an official 
-2020 for more information.+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, complete 
 +procedures for canary verification has been added. 
 + 
 +Canary Verification Procedures 
 +~~~~~~~~~~~~~~~~~~~~~~~~ 
 + 
 +1. To verify biergaizi's signature... 
 + 
 +    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. 
 + 
 +    d. Fetch vimacs' new public key from https://keys.openpgp.org, using the same 
 +    fingerprint, and import the public key. You should see that the public 
 +    key has been updated. 
 + 
 +    e. Please note that the key is still shown as "expired" because the new key 
 +    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" warning (because the latest UID is 
 +    not published, only the expired UIDs are available).
  
 Proof of Freshness Proof of Freshness
Line 78: Line 154:
  
 $ 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
- The Briefing: Sign up for two-minute audio news updates on WhatsApp, Apple, Spotify and Alexa twice a day + Travel restriction updates: Antibody tests could allow holidays to resume 
- Boris Johnson baby latest newsPM to take paternity leave later this year as he focuses on coronavirus crisis + Clap For Our Carers: what time is the NHS applause tonight
- What is coronavirus, how did it start and how big could it get+ Suicide bomb in eastern Afghanistan kills five 
- How many coronavirus cases are in the UK - and where are they? + ExclusiveSecond more deadly wave of coronavirus 'to hit Europe this winter' 
- Wednesday evening news briefingPM and Carrie's baby joy+ Can I take ibuprofen to treat coronavirus symptoms? Expert advice on painkillers and Covid-19
  
 $ 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
- Coronavirus World News: Live Updates +
- China Sets Date for Congress, Signaling Coronavirus Is Under Control +
- Boris Johnson and Carrie Symonds Have a Baby Boy +
- This Isnt the Time for Caviar: A Chef Finds New Flavors in a Pandemic +
- Fire at Construction Site Kills 38 in South Korea+
  
 $ date -R -u $ date -R -u
-Wed29 Apr 2020 18:39:36 +0000+Thu14 May 2020 12:45:15 +0000
  
 -----BEGIN PGP SIGNATURE----- -----BEGIN PGP SIGNATURE-----
  
-iQIzBAEBCgAdFiEE3n2KYOSW/nkFgy0Or5D/NPDHQYQFAl6qsrQACgkQr5D/NPDH +iHUEARYKAB0WIQSk6G5G0KgwQYRNdeEkSefAFKcZwAUCXr09iwAKCRAkSefAFKcZ 
-QYSdehAAgdmN9fI7HsJvXunK/MNozpqNX+CvZj3mXN3S42SwZaZo0qagg3Rds687 +wGEoAQCgFBMOWin6oU9AFxNJikPxflehBY2hEnmhyop45y39xAEAhIVW595KP0N3 
-kNJDLzOJVlBJ3GpsVNjVyvyIkzkK8vIFLCBkGG4w8+GySa+3vo7QjOiyqo69RkBV +c05lwIm4kGUmsrbkgeRAI1nLxOECSwg
-Rzq3PHoT6dm4qRuw1MS0c+TQ8iavMKcv44MtmC3WANJmKWzh8xkyXR/rorm0sfM2 +=RP5g
-N6EDX5v3RTNet5mv808k9X1qxL2GQP9gRjVCCKNKFZZbMgKZ1bY2WAIxC60U75En +
-EU4PXtOUjCcgxIs9qMVyeMoEJsCqLgkJKmXjQnx+U0OczeWqB/7VhM94T817XQoa +
-0OUtbri1Wd2krvPmgaynMC8Mj5vy6ASSZhXPxC3ES2eMSNEi+ZF5MMkdl152Hh/+
-DmqjsTJqzr7lBx+07DjoONFJfsPUB/ctMM6viGyiGSUfqL4yjq8kgb4hdfAvwq6O +
-XuVCJm/nsPjogAeQkO4ic0BakWjFhwSe76nZnR37EIXcFqzVswdeAJRH9q6KRBH/ +
-3pqsTdJOP8u5NjgLsvgBLNNcGe5KXKoNN8dPF/ucwqfzwOwZ8XHar6ImA4n9VeDV +
-7S1vufxdcOI6ZaFBiO6uY2mAtwa+3O/0XzOMsKJSoKDGQZtUQOLHUYalolgxqAx4 +
-91U5RIXEJlydWMd8cMmksReCMwv2lG6NTZ2krP+TFHN/OFdrdEE+
-=Z+oq+
 -----END PGP SIGNATURE----- -----END PGP SIGNATURE-----
 +
 </code> </code>
  
blug-canary-3.txt · Last modified: 2020/07/15 15:14 by vimacs