>>19022

^tldr: digital signature tripcode (why not both)

If we do this, the first time Q would:

Install OpenSSL

run cmd.exe if on Windows

openssl genrsa -out private.pem 4096 (<-- make the private key file)

openssl rsa -in private.pem -pubout -out public.pem (<-- make the public key file)

openssl rsa -pubin public.pem -text (<-- print out the public/verification key as base64 text)

This gets posted and Anons save it as file public.pem in the directory they are going to save Q messages/run OpenSSL (only need to do once)

Then for every message Q would do: (if the message is message1.txt)

openssl dgst -sha256 -sign private.pem -out message1.sha message1.txt (<-- hashes message1.txt and digitally signs the hash)

openssl base64 -in message1.sha -out message1.b64 (<-- turns the signed hash into printable characters that can be pasted)

Anons would save this signature as message1.b64 and the rest of the post as message1.txt (for instance), then run:

openssl base64 -d -in message1.b64 -out message1.sha (<-- make the post text into format for verification)

openssl dgst -sha256 -verify public.pem -signature message1.sha message1.txt (<-- check if the key that signed the message goes with your public key/belongs to Q)

Results are:

Verification Failure

or

Verified OK

You don't have to type all this in every time or even use the command line. In windows you can set it up to run the commands when you click a desktop shortcut so all the time is in saving the text.

It's important not to get spaces when copying that weren't covered in the signature because it has to be exact. That should be easy to do though and you can try your copy boundary in all the likely looking places.

Godspeed Trump, Q and team