Archives of historical canaries can be found at:

https://github.com/beijinglug/warrant-canary

If you are using Tor, please check the canary documents from the clearnet domain instead of Tor hidden service, since the links within the messages are modified to “.onion” and invalidate PGP signatures. Or go to GitHub archives from the link above.

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

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

Issued for August 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-2

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 September 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
 Stephen Port: Families of serial killer's victims compensated after Met failings
 Tuesday morning news briefing: Statins 'myth debunked'
 Notting Hill Carnival stabbing: Man, 21, dies after attack
 Daniel Craig: My mission to end barbaric cluster bombs killing Ukrainians
 Albanian migrants crossing the Channel to face criminal records checks at Dover

$ rsstail -1 -n5 -N -u https://rss.nytimes.com/services/xml/rss/nyt/World.xml
 Ukraine Announces Offensive in Kherson, as Inspectors Head to Nuclear Plant
 More Vital Than Ever, Ukraines Trains Bind a Land Fractured by War
 Iraq Clashes Leave 12 Dead After Muqtada al-Sadr Says Hes Leaving Politics
 As Rome Burns (or at Least Its Garbage), a Mayor Dares to Dream
 Ukraine Announces Push in South; U.N. Inspectors Head to Nuclear Site

$ date -R -u
Tue, 30 Aug 2022 08:48:44 +0000

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

iQIzBAEBCgAdFiEEJVIRsjlaWj4OSKDx+tPrBeiOjW0FAmMNzy8ACgkQ+tPrBeiO
jW2kiQ//ZaWAlsP+lYReSB/69Y+M3B162ajp2ohfc3883Pl6cloMEK3LzIWZ9K6G
Vk9YA3BhQE4GDA3vlNIi6Nx7jpl0nWq0S2FuUErlHbj9F5AueanMKSVX9o1fGoIW
hElZlgXdmcyIWF7gIn2gTabt6440xSGseyPoIa5Unz9wIHVG9QSiIxi7efMpafTg
vADyE+N6IdvuVa4QY7xkl9VQMb9/Z66DyKjtSVd/WG5G6Zkn1opy7dkRIv1Om4dK
YEh5+1FlIAjyg3fwmI/H4jlTLfjsyKmMA6t+BGhR+q5RDGG0tmFx3ltkpdDcNwbj
sk1yGYNmiyu1VEp7EeH2KPa0UGTgzxR+DZCQ0n087qIdXV3yNDbPDx/In60ddpKq
iOUdLe2yCL9ErLgT7k9tQvun7VWZOO4rxvW01cquromBFO+foQX/NQKuM+n+dLgO
ZRwqfX4MuVgMCAEiGoQoA9MMZ2H2nAqoeuL83y0Zk7kGxaTfbkuwNNnkrNF8bH+t
E/UdMAaYZU00a64A0fVbj5SQ5zpGOp2v1ahegke/hrl2xlAA+TTVvb/0lA/I7Akx
jhsl+U7cP667E7gkpyi7ivkZkcytCLGLjan9ne0jTqkOBW2yVxv6fFVIV9k7Y63J
fBZp0w3Gl553vvNLFfHBNO/wjdYSAZ63sb2shEDdU1hqHOnGKx0=
=HNX5
-----END PGP SIGNATURE-----