The real trick is picking a private key that gives you human-readable phrases in the public key.
I had a train of thought that ended up with human readable tripcodes, but I forgot how I got there.
Anyway, if you want your 4chan tripcode to have “farts” in it, use “Aq5wJetM” as your password :
https://m4c4r0n1n.github.io/Tripcode-Generator/
Password (click to copy) Tripcode Matched Aq5wJetM ◆C0qfartsTY fartsCock farts thank you
So it’s not just me.
…
At least it’s not just me.
I see you
you also crossed out 69
At the top, fellow Brazilians will recognize foda
No “caralho” though.
If you’re using an insecure private key that’s your fault not let’s encrypts.
Why are there always so many AA’s in these things?
AA… is the BASE64 encoding of 00…
Keys are binary, so wouldn’t those be nils (or
00000000)?This turned out to be more interesting than I thought. No idea why, I just assumed these were b64 encoded random giant bit strings, so zeros were just as likely as any other value.
Usually the key format is not only a number but an ASN.1 (https://en.wikipedia.org/wiki/ASN.1 ) encoded data structure, with many different fields for metadata, usage restrictions etc, so a lot of the bytes you have in there are actually not random at all.
That text could have been the private key (as the joke implies), or could have been a metadata field which just gets ignored and signed by the CA.
