Timeline for What's the difference between X.509 and PKCS#7 Certificate?
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 29 at 17:40 | comment | added | fourpastmidnight |
@SergeyPonomarev If I had to guess why Windows shows a different description for .p7c vs .p7b, the c would stand for certificate, meaning one certificate, while b would stand for bundle (or as Windows shows, Certificates PKCS #7), or multiple certificates are contained therein. However, if you were to rename the .p7b file to .p7c, or vice versa, it would still be valid--as it's still a PKCS #7-formatted file.
|
|
| Oct 25, 2023 at 7:23 | comment | added | Sergey Ponomarev | @dave_thompson_085 thank you. The Kleopatra program uses p7s for signatures (both attached and detached) and the p7m for encrypted. They also are registered in the share-mime-info so all Linux distros knows this extensions and shows an icon for them. Windows and macOS also know them. I wasn't able to find a program that generates p7c but it should contains a cert only while p7b chain of certificates. I added them to en.wikipedia.org/wiki/X.509#Certificate_filename_extensions | |
| Oct 24, 2023 at 1:06 | comment | added | dave_thompson_085 | @SergeyPonomarev (sorry for delay, I couldn't refind you in my overfull pending box): in general only Microsoft cares about file extensions. I know many programs that create or read (or both) the PKCS7-certs-only format (and have written some myself) but they can use any extension the user chooses; p7b and p7c are only conventions and (often) defaults. FWIW p7c -- but not p7b -- is published in the SMIME RFCs (2633, 3851, 5751, now 8551). | |
| Oct 13, 2023 at 18:15 | comment | added | Sergey Ponomarev | BTW is any specification for the file extensions? | |
| Oct 13, 2023 at 18:14 | comment | added | Sergey Ponomarev | for the .p7c the Windows Explorer shows a file type "Certificate" but for the .p7b it shows "CertificateS PKCS #7". So as far I understood the .p7c is only one cert while the .p7b is a full chain. Could you clarify on this? Do you know any program that generates the .p7c? | |
| Oct 7, 2021 at 8:14 | history | edited | CommunityBot |
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
| Oct 7, 2021 at 7:05 | history | edited | CommunityBot |
replaced http://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
|
|
| S Apr 28, 2019 at 4:21 | history | suggested | Cristian Ciupitu | CC BY-SA 4.0 |
improved formatting
|
| Apr 27, 2019 at 19:16 | review | Suggested edits | |||
| S Apr 28, 2019 at 4:21 | |||||
| Apr 29, 2018 at 8:19 | history | edited | dave_thompson_085 | CC BY-SA 3.0 |
added 285 characters in body
|
| Dec 2, 2017 at 3:21 | history | edited | dave_thompson_085 | CC BY-SA 3.0 |
added 339 characters in body
|
| Nov 21, 2014 at 11:48 | comment | added | dave_thompson_085 |
@Thomas good point, edited. And the same for SignedData that does convey a signature (or several), but that's out of scope for this question.
|
|
| Nov 21, 2014 at 11:46 | history | edited | dave_thompson_085 | CC BY-SA 3.0 |
clarify set-of certs as suggested by @Thomas
|
| Nov 20, 2014 at 12:30 | vote | accept | golem | ||
| Nov 19, 2014 at 18:14 | comment | added | Thomas Pornin |
It may be worth mentioning that a PKCS#7/CMS SignedData structure used as a mere bag for certificates is unordered: you can put several certificates, but the format does not keep track of any ordering. Therefore, it can transport a certificate chain exactly as well as IKEA sells furniture. Decoders must still work out who signed who in the chain.
|
|
| Nov 19, 2014 at 16:01 | history | answered | dave_thompson_085 | CC BY-SA 3.0 |