all 11 comments

sorted by: hot top controversial new old
[–] 79 points 3 days ago (3 children)

The real trick is picking a private key that gives you human-readable phrases in the public key.

  • source
  • hideshow 3 child comments
  • [–] 32 points 3 days ago* (2 children)

    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	       farts
    
  • source
  • parent
  • hideshow 2 child comments
  • [–] 32 points 3 days ago

    If you’re using an insecure private key that’s your fault not let’s encrypts.

  • source
  • [–] 21 points 3 days ago (3 children)
  • [–] 17 points 3 days ago (1 child)

    Why are there always so many AA’s in these things?

  • source
  • hideshow 1 child comment
  • [–] 11 points 3 days ago

    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.

  • source
  • parent