22 The B<pkcs7> command processes PKCS#7 files in DER or PEM format.
24 =head1 COMMAND OPTIONS
28 =item B<-inform DER|PEM>
30 This specifies the input format. B<DER> format is DER encoded PKCS#7
31 v1.5 structure.B<PEM> (the default) is a base64 encoded version of
32 the DER form with header and footer lines.
34 =item B<-outform DER|PEM>
36 This specifies the output format, the options have the same meaning as the
41 This specifies the input filename to read from or standard input if this
42 option is not specified.
44 =item B<-out filename>
46 specifies the output filename to write to or standard output by
51 prints out any certificates or CRLs contained in the file. They are
52 preceded by their subject and issuer names in one line format.
56 prints out certificates details in full rather than just subject and
61 don't output the encoded version of the PKCS#7 structure (or certificates
62 is B<-print_certs> is set).
66 specifying an engine (by its unique B<id> string) will cause B<pkcs7>
67 to attempt to obtain a functional reference to the specified engine,
68 thus initialising it if needed. The engine will then be set as the default
69 for all available algorithms.
75 Convert a PKCS#7 file from PEM to DER:
77 openssl pkcs7 -in file.pem -outform DER -out file.der
79 Output all certificates in a file:
81 openssl pkcs7 -in file.pem -print_certs -out certs.pem
85 The PEM PKCS#7 format uses the header and footer lines:
90 For compatibility with some CAs it will also accept:
92 -----BEGIN CERTIFICATE-----
93 -----END CERTIFICATE-----
97 There is no option to print out all the fields of a PKCS#7 file.
99 This PKCS#7 routines only understand PKCS#7 v 1.5 as specified in RFC2315 they
100 cannot currently parse, for example, the new CMS as described in RFC2630.
104 L<crl2pkcs7(1)|crl2pkcs7(1)>