Timeline for What is the technical name for a public key container in DER format?
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 6:47 | history | edited | CommunityBot | replaced http://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc | |
| Sep 29, 2014 at 16:02 | vote | accept | mpontillo | ||
| Sep 29, 2014 at 12:40 | history | tweeted | twitter.com/#!/StackCrypto/status/516568146728067073 | ||
| Sep 17, 2014 at 8:50 | comment | added | Maarten Bodewes♦ | I do not agree with the close votes. This is not about decoding or decrypting a piece of ciphertext, it is about identifying a cryptography related data structure. That is both a concise question and of use to others. | |
| Sep 16, 2014 at 20:06 | answer | added | mpontillo | timeline score: 2 | |
| Sep 16, 2014 at 5:29 | history | edited | otus | edited tags | |
| Sep 15, 2014 at 23:35 | comment | added | mpontillo | @HenrickHellström, bingo, that is exactly what this is. Thank you. If you make that an answer, I will accept it. (for what it's worth) | |
| Sep 15, 2014 at 23:33 | comment | added | Henrick Hellström | If it's not a plain PKCS#1 RSAPublicKey, it is probably a SubjectPublicKeyInfo from PKIX/X.509 | |
| Sep 15, 2014 at 23:33 | history | edited | mpontillo | CC BY-SA 3.0 | edited title |
| Sep 15, 2014 at 23:24 | comment | added | mpontillo | Just to be clear (and as I mentioned in a previous comment), you are correct that PKCS#1 specifies the contents of the BIT STRING shown in my example. But I'm asking what the name of the entire object is. | |
| Sep 15, 2014 at 23:19 | review | Close votes | |||
| Sep 25, 2014 at 23:10 | |||||
| Sep 15, 2014 at 23:19 | comment | added | mpontillo | @HenrickHellström, I have been doing pretty much exactly that, and I don't know what to call this code module. PKCS#1 certainly doesn't fit. This format can clearly be used for non-RSA key types. | |
| Sep 15, 2014 at 23:17 | comment | added | Henrick Hellström | Well, you don't have to take my word for it. All you have to do is to implement a Base64 decoder, an ASN.1 parser, a DER parser and see for yourself, just like I did. :) | |
| Sep 15, 2014 at 23:09 | comment | added | mpontillo | @HenrickHellström, the question of off/on topic aside, I don't necessarily agree. First, it's DER, not PEM. (the contents of the PEM header in my example are not relevant to the discussion.) Second, I checked RFC 3447 (PKCS#1 v2.1) and didn't see any mention of this particular format. To be specific, section A.1.1 mentions the public key syntax, but not the PKCS#8-like wrapping my example exhibits. (see the rsaEncryption OID in the asn1parse output.) | |
| Sep 15, 2014 at 23:03 | comment | added | Henrick Hellström | The format is PKCS#1 with PEM encoding. Your question is however off topic here. | |
| Sep 15, 2014 at 22:59 | history | asked | mpontillo | CC BY-SA 3.0 |