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

BEIJING GNU/LINUX USER GROUP CANARY (3/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-1

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.

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

0. Due to an oversight, the third canary document for September 2021 was not
signed by vimacs on time. However, all the Statements were and are still valid.
The missing document for September was retroactively generated in October 2021.
To further ensure the validity of the Statements and Special Announcements,
this canary document for October 2021 is modified to include this statement.

2. Outdated information about vimacs becoming a new signer after the departure
of wnereiz has been removed.

3. 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 and updated.

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
 Omicron symptoms: How long they last and how the Covid variant differs to previous strains
 The schools that send the most pupils to every Oxford and Cambridge college
 Chinese New Year 2022: Everything you need to know about the Year of the Tiger
 Police name the 12 most wanted British fugitives on the run in Spain
 Wednesday morning UK news briefing: Plot to topple Boris Johnson

$ rsstail -1 -n5 -N -u https://rss.nytimes.com/services/xml/rss/nyt/World.xml
 China's Rising Menace Hardens Taiwan's Separate Identity
 After Volcanic Eruption, Tonga Faces Weeks Without Internet
 As Johnson Reels From Scandals, Is Someone Plotting to Take His Place?
 Blinken to Meet With Russia as U.S. Pushes For More Diplomacy on Ukraine
 Italy Ponders a New Role for Draghi. Let the Politicking Begin.

$ date -R -u
Wed, 19 Jan 2022 12:42:41 +0000

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

iHUEARYKAB0WIQSk6G5G0KgwQYRNdeEkSefAFKcZwAUCYegHZAAKCRAkSefAFKcZ
wMZhAP9UvxXsZnMFSvAG56X5y2N2UYHdKMIp6KiBwczry3TbkgD/T5G+sJuLVZLm
8/HgQI92+i0wgvRa5nRtTsAyr+lpKAo=
=QDrM
-----END PGP SIGNATURE-----