BLUG Wiki

This is an old revision of the document!

---

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

BEIJING GNU/LINUX USER GROUP CANARY (2/3)
====================================

Issued for January 2022.

Don't just trust the contents of this file blindly! Verify the
digital signatures! Also, make sure the keys are correct!

Signers
~~~~~~~~~~~~~

* biergaizi: 0x255211B2395A5A3E0E48A0F1FAD3EB05E88E8D6D
* persmule : 0xEDFFE248ECFACDE3C805906804A40D21DBB89B60
* vimacs   : 0x7079B481F04B5D8B65A0ECDEEA2DB82FE04A9403

THREE DOCUMENTS IN TOTAL.

You should verify all signatures from each of the maintainers, the next
one is located at:

* https://beijinglug.club/wiki/doku.php?id=blug-canary-3

It is possible that the signatures are not updated at the same time,
but eventually all canary documents should be consistent, signed and updated
by all current maintainers of Beijing GNU/Linux User Group in a short time.

Statements
~~~~~~~~~~~~~

1. All our infrastructure is in our control, the integrity of our
entire system is sound.

2. We have not been compromised or suffered a recent data breach,
to our best knowledge.

3. We have not disclosed any private encryption keys.

4. We have not been forced to modify our system to allow access or
information leakage to a third party.

5. We haven't received any specific orders, requests or recommendations
from any authorities, whether formal or informal.

6. We have not received any court orders, gag orders, or other similar
orders from the government of the People's Republic of China.

7. We have not received any government subpoenas.

8. Our personal safety and security is not threatened.

9. To avoid security breaches and emphasize the clarity of the warrant canary
documents, if a signer is temporarily unavailable, only existing signers in the
"Signer" list SHALL sign a special placeholder notice (this notice itself SHOULD
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 warrant
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
weeks of February 2022. Special note should be taken if no new canary is published
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, complete
procedures for canary verification is included here.

Special Announcements
~~~~~~~~~~~~~~~~~~~~~~~~

None.

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. Obtain the public key from any traditional OpenPGP Keyserver, such as
    https://keyserver.ubuntu.com, and import the public key. The fingerprint
    is 0x7079B481F04B5D8B65A0ECDEEA2DB82FE04A9403.

    b. Use the latest GnuPG in any operating system.

Proof of Freshness
~~~~~~~~~~~~~~~~~~~~

$ rsstail -1 -n5 -N -u https://www.telegraph.co.uk/news/rss.xml
 River Thames has become an open sewer as treatment plants overwhelmed, report finds
 Friday evening UK news briefing: US and Russia in tense Ukraine standoff
 Alexa down: Amazon outage leaves users unable to access smart speakers and smart devices
 Babes in the Wood killer Russell Bishop dies
 Omicron symptoms: How long they last and how the Covid variant differs to previous strains

$ rsstail -1 -n5 -N -u https://rss.nytimes.com/services/xml/rss/nyt/World.xml
 U.S. and Russia Take More Measured Stance in Ukraine Talks
 How a Volcano Severed Tonga From the World
 China Holds the Line on Zero Covid, but Some Wonder for How Long
 Viral Photograph of Munzir El Nezzel Helps Bring Syrian Refugee Family to Italy
 80 Years Ago the Nazis Planned the Final Solution. It Took 90 Minutes.

$ date -R -u
Sat, 22 Jan 2022 04:02:50 +0000

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEE+SOCpROWPk6Sp6Iw8P4UaDjldeAFAmHrgvIACgkQ8P4UaDjl
deDxigf+Opopar8T539m8Lq+Zkyz75HwkQsxONRO5XMv4fnWchNZ6wqdR2w4WJL9
kkSKMCqh5CGYkEcS15nKZfwRyrf5NS9pfbfl4fvZsX/a9fhWRsvpPQSU/PjL2eHm
UAmxrGBHNq6uNDcjJaB6yYg36mCi2oY8VrO8Us2GXrLo9mg/zdYGe7RbafKwtQIc
8TXowIvR8mmQ7p0ekG0XGeUjz+RuKEYtYZNmcrOGzBlJ4k4QlwKhbSCDyWyMhlpz
jmHYSmwxFHqe6R172r4VMg2gJ9C1P5eC8ine9it+b1u4C7FX4ZpRKZXFk+0qgFlp
5I6lGusLQIETuc+PS1ersPlUrLrZtQ==
=hvhL
-----END PGP SIGNATURE-----