I created a GnuPG signing key pair yesterday which I posted on a key server.

gpg –fingerprint "Q Anon Supporter"

pub rsa4096 2018-04-22 [SC] [expires: 2019-04-22]

CB03 B1E2 539E 68AD 64CD 812D 05F3 44D8 7098 EEF6

uid [ultimate] Q Anon Supporter (Anonymous Q Anon Supporter)

Q is currently using a "trip code" so that we can verify his communication with us. I propose that we start using a GnuPG signing key so that each message can be verified as an original. All you have to do is copy the portion below that begins with

—–BEGIN PGP SIGNED MESSAGE—–

and ends with

—–END PGP SIGNATURE—–

into your favourite text editor like nano, vim, or emacs (sorry I do not know what M$ is currently using) and save the file as anyname.asc

Then you can verify it using

gpg –verify anyname.asc to see if the message has been altered or changed by some nefarious creature.

—–BEGIN PGP SIGNED MESSAGE—–

Hash: SHA512

Hi all,

I want to address this message to all of the

paranoid Q Anon supporters out there. There

are many who read this board and trust the

trip code that Q uses. I would like to see

an open pgp signing method using an open

source tool like GnuPG.

When you create an anonymous key using:

gpg –full-gen-key

leave the email field empty or enter a bogus

email address.

After you create your key, use

gpg –send-key key-ID

to send your key to a key server so others can

retrive your public key to verify your posts.

There are many on the dark web who are using

8ch.net/qresearch/ who are not friends and

are doing their best to create a NWO!

We must upgrade our security practices for

our own protection.

This message was created using:

gpg -u "Q Anon Supporter" –clearsign QAnon-Test-Message

This comand creates the file QAnon-Test-Message.asc

This message can be verified by:

gpg –verify QAnon-Test-Message

I hope that this is helpful,

Q Anon Supporter

—–BEGIN PGP SIGNATURE—–

iQIzBAEBCgAdFiEEywOx4lOeaK1kzYEtBfNE2HCY7vYFAlrdOjwACgkQBfNE2HCY

7va2TQ/9HiExFhPe9w00jtIQmhXwEnHCMl0o9JRgyQclV9nenJH1G+mblqm10tNY

1uRerlSxH7XhiiRvXMRhqzzkNvbAW6xVsz5umOpM2e6F4UkojwL7WELE1PEJlWV+

xAGiXx1xe6HjFA9ECSITm3uAzG4HNkoBbhNmD+KJlqX8eXIt0XX166+5G2jRMY4W

QkKwvMLSEj56mn66SqaQ8VorQo4N/Y+t9g6v3MDVybEehy3QmFEddwK7lx+FbrDz

8b3NZ/G9Jq2OBKzPC8M6uJThgrzjG1ShqF73h6HlivcckgR3lw54EoQvO/TmLNg+

FAJtfQJkX9iYrFFT35wJYWpCg2OUXUi9oLTLMMwkV+E3NRslwg6H7+DWcd9j01zt

vxPWa+ESRMEYCJZjeYrarEep5d6SBOcFVScK9yasnslErx458hL/xYMj/WspsO94

PlomQ4b18JfZCn3/xSfZOiXCH3aokamTWLKrBskvqMxGYC3TUP1dy0nQDgI2d37l

pC2cf8lY9/qYREbUKmTY2mPjO4S/AjKCJc7SlOdweAfZj9VnbwlaGe9AxzIzK2gM

yG+/oaiBm8lsWDKkNXCNfYFIyYr2ZPYaljphQWzvnAfjpSWOn9X/9u5zqkkTD8oQ

ZHj3SovXlODQGGmXja+RnQqVPVC6fjXxtTSLBvqPY+gz4J0GnuY=

=KKrS

—–END PGP SIGNATURE—–

I thought using GnuPG would be a good idea, but I discovered that 8ch.net adds additional carriage returns and line feeds and also changes the 5 hyphens into 2 long dashes thus the message cannot be verified.

$ gpg –verify test.asc

gpg: no valid OpenPGP data found.

gpg: the signature could not be verified.

Please remember that the signature file (.sig or .asc)

should be the first file given on the command line.

Good idea, but not feasible at the present time.