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 [2019/09/30 17:44] BLUG Admin old revision restored (2019/07/24 03:57) |
blug-canary-2 [2020/05/14 12:40] persmule |
||
---|---|---|---|
Line 8: | Line 8: | ||
==================================== | ==================================== | ||
- | Issued for July 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 16: | ||
~~~~~~~~~~~~~ | ~~~~~~~~~~~~~ | ||
- | * biergaizi: | + | * biergaizi: |
- | * persmule : 0x2987A25DAC8454A5 | + | * persmule : 0xEDFFE248ECFACDE3C805906804A40D21DBB89B60 |
- | * wnereiz | + | * vimacs |
THREE DOCUMENTS IN TOTAL. | THREE DOCUMENTS IN TOTAL. | ||
Line 55: | Line 55: | ||
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 August 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 69: | ||
~~~~~~~~~~~~~~~~~~~~~~~~ | ~~~~~~~~~~~~~~~~~~~~~~~~ | ||
- | 1. Due to personal reasons, wnereiz (0xFDFF2E13AA25BE72) | + | 1. Due to personal reasons, wnereiz (0xFDFF2E13AA25BE72) |
- | couldn' | + | 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 | ||
+ | decision that can be verified by checking | ||
+ | signed by wneriez. | ||
- | 2. We determined that this was not a result of any incident. All statements of | + | 2. In the previously mentioned document designed by wneriez in April 2020, |
- | the warrent canary documents are still valid. Furthermore, wnereiz will continue | + | the date in its statements was mistakenly written as "April 15th, 2019", |
- | to sign the canary documents in the future. | + | 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. We determined that the decision of asking | + | 3. A new member, |
- | replace wnereiz and sign a substitution | + | month. You can validate the new keys by cross-checking the other two copies |
- | decision is thus revoked. | + | this document, signed by biergaizi and persmule. |
- | 4. To avoid future incidents, we have amended | + | 4. Due to the ongoing security issues of OpenPGP keyservers, it makes signature |
- | canary documents, and added a new Statement to prevent similar issues. | + | verification an issue and somewhat |
+ | procedures for canary verification has been added. | ||
- | 5. The previous warrent canary documents issued | + | Canary Verification Procedures |
- | this version | + | ~~~~~~~~~~~~~~~~~~~~~~~~ |
+ | |||
+ | 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 | ||
+ | 3rd-party to verify the canary document signed by persmule. | ||
+ | |||
+ | b. We are looking for a solution. But for now, you should check the | ||
+ | | ||
+ | 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:// | ||
+ | | ||
+ | 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 90: | Line 155: | ||
$ rsstail -1 -n5 -N -u https:// | $ rsstail -1 -n5 -N -u https:// | ||
- | Sri Lanka accuses UK of hiding human remains | + | Travel restriction updates: Antibody tests could allow holidays to resume |
- | Booker Prize longlist 2019: The 1,000-page novel with only one sentence | + | Clap For Our Carers: what time is the NHS applause tonight? |
- | | + | |
- | Give heatwaves names so people | + | Exclusive: Second more deadly wave of coronavirus |
- | | + | Can I take ibuprofen to treat coronavirus symptoms? Expert advice on painkillers and Covid-19 |
$ rsstail -1 -n5 -N -u https:// | $ rsstail -1 -n5 -N -u https:// | ||
- | For Boris Johnson, the Tumult Begins Inside Downing Street | + | Coronavirus World Updates |
- | Boris Johnson | + | Born Into Carnage, 18 Afghan Babies Face an Uncertain Fate |
- | Trump and Johnson: Allies in Disruption | + | Inside China' |
- | In Pakistan, a Feminist Hero Is Under Fire and on the Run | + | Outside Egypt, Critics Speak Freely. Inside, Families Pay the Price. |
- | South Korean Jets Fire Warning Shots Toward Russian Military Plane | + | Duterte' |
$ date -R -u | $ date -R -u | ||
- | Wed, 24 Jul 2019 03:53:59 +0000 | + | Thu, 14 May 2020 12:35:27 +0000 |
-----BEGIN PGP SIGNATURE----- | -----BEGIN PGP SIGNATURE----- | ||
- | iQIzBAEBCgAdFiEEfpRElbj/ | + | iQEzBAEBCgAdFiEEwonfPqgFyacM7J3iwYAPuUJ74CEFAl69OxsACgkQwYAPuUJ7 |
- | sm3wUhAAvIgywMOmEkiqyHsYx7f2asOPKEFzUKzaLHHlp8cxRSgfeG4bu3QiXSK8 | + | 4CENcwf/fXxmuSk2jZh67on74z8JB+RX5UJIcfs7fDOeoQuAZ7xN/cT/Rqe71dhn |
- | / | + | jb9rpgAPUtg1eTeX+tN3B2ucCvDkLjzeHGRj7vzlW3acupiCuu1lHlQhoEDH3lBP |
- | ULNLMoMShLoWNkDZxMVtcpG3+1/akAbSqUxkntSESM736kl4Tm6JH/s9E5LQxHVw | + | HF58RQwrYRoPpA4zfCXsp4cfNj5MVd9DL1Gm6QPm/tqkIQr1q4cMT5OfDoYBUAsf |
- | Q5hJP5PPwCEpPXUharjnptudxcSVa64MDKJfGW+Pv99lKRCN/ | + | XK0Gk3oBHXNJVjuImYf27Yzh/o2qS1jAo2r/8iaEqxmYet3fvobX7HikbsJgXLV9 |
- | T6sfW2qYCyRDXFvVuEIHOT/3u3ubg1+zsDoEWC+Z4o+FixgndnrJ9RYWaM2AWbqD | + | 29jAaI/rkAsZ8LCtoRkZFhpk8r7ORYbs0pSzmxTW0fXlH3BhNErnQKgNG79JxPyh |
- | LlNxbNvssD0qozv2TpTr2xhJo//EDht37hCQ8TsyMdOgj/ | + | oHfYkK5sykO5z5ga+kJ4baPxo1MKWQ== |
- | jY7c2yJmlWUehqymVZSFn9D997o0VyymeZQmFbg4Zqdvm2uJxfhB6xj3GslYsvHl | + | =XEKh |
- | C0M9V7bTqTrqgH/ | + | |
- | LZFvgglXMiwDE/ | + | |
- | HXmDQwYKgnSNqIa7fpWvw2Shi5Qrnch1G8o3YvVCqYxUVAO6BLuGgiGO2PLaxiWE | + | |
- | 0HeNR1fnvlwllujTj21iAJZI/ | + | |
- | =nNSR | + | |
-----END PGP SIGNATURE----- | -----END PGP SIGNATURE----- | ||
</ | </ |