technicallyCorrectFormat

[u/precinct209]

[u/MrFarby]

where did you find 384 bit numbers ????

[u/Sibula97 → u/MrFarby]

https://en.wikipedia.org/wiki/P-384

[u/MrFarby → u/Sibula97]

Thanks, that's going on the list to learn more about later

[u/Goheeca → u/MrFarby]

You can checkout my Haskell project, I have P384 there.

---

^{If you're using free-tier BitBucket repos and are inactive there, back them up, they're disabling workspaces and subsequently they'll permanently delete them.}

[u/MrFarby → u/Goheeca]

I'm not learning haskell rn, but it is on the list, so i guess these two entries are geting bundelled 😭

[u/Crimento]

It's even funnier in binary

[u/Cheyomi832 → u/Crimento]

00000000 00000000 00000000

00000000 00000000 00000000

00000000 00000000 00000000

00000000 00000000 00000000

00000000 00000000 00000100

[u/Old-Awareness4657]

Biblically accurate private key 

[u/nsefan → u/Old-Awareness4657]

“BE NOT INSECURE”

[u/DrDam8584]

In fact it is a number as random as any others, mainly improbable.

[u/laplongejr → u/DrDam8584]

Not when the company who made the key announced that they accidentally used a key from a testing script which produces small keys...  

[u/gene66]

…0000100

[u/buzzon → u/gene66]

It's hexadecimal, not binary

[u/DontDoodleTheNoodle → u/buzzon]

Frickin’ witches and their hexes…

[u/Grintor]

The correct format is more like

-----BEGIN EC PRIVATE KEY-----
4===
-----END EC PRIVATE KEY-----

[u/0x0MG → u/Grintor]

You can't have three padding characters like that in base64 encoding. It'd be

-----BEGIN EC PRIVATE KEY-----
BA==
-----END EC PRIVATE KEY-----

[u/No-Magazine-2739 → u/Grintor]

Even its even go short for base64 without padding.

[u/redditsucksass69765]

It’s a perfectly cromulent random 384-but number

[u/die_liebe]

Where do these joke about 4 come from?

[u/Gordahnculous → u/die_liebe]

eMuhdra, an Indian e-commerce company that up until recently provided TLS certs, had one of their private keys for their TLS certs being 4

There were 7 other private keys of theirs that were also less than 255 (decimal) but 4 is definitely the wildest one of the 8

[u/NatoBoram]

Quite a few people claim the key would be just the number 4 in base64 but if you actually try to generate one, you'll get something like this:

-----BEGIN EC PRIVATE KEY-----
MHcCAQEEIAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEoAoGCCqGSM49
AwEHoUQDQgAE4lNKNTLQj7ugLd5lnuYr0AMf4tt4VZbvUJMCRGsDCFLg8VdaTGM8
xxnf7l/ahi12TvyWw/MO4AVcQsI/GE7Yxg==
-----END EC PRIVATE KEY-----

Save it in key.pem and do openssl pkey -in key.pem -text -noout on it then you'll see this:

Private-Key: (256 bit)
priv:
    00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:
    00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:
    00:04
pub:
    04:e2:53:4a:35:32:d0:8f:bb:a0:2d:de:65:9e:e6:
    2b:d0:03:1f:e2:db:78:55:96:ef:50:93:02:44:6b:
    03:08:52:e0:f1:57:5a:4c:63:3c:c7:19:df:ee:5f:
    da:86:2d:76:4e:fc:96:c3:f3:0e:e0:05:5c:42:c2:
    3f:18:4e:d8:c6
ASN1 OID: prime256v1
NIST CURVE: P-256

[u/cAtloVeR9998 → u/NatoBoram]

That last E after the string of As is all the entropy you need for an intermediate certificate’s key.

[u/Single-Virus4935]

The key ist stored with leading zeros but a variable length encoding. So it is max 1byte

[u/GigaSoup]

The best kind of correct!

[u/TomatilloNo8486]

Excuse me, I might not understand the basics of cryptography but I have a handle on compression

[u/Jamichiri]

-1 = 0xFFF...FFF