1PKCS7(1) OpenSSL PKCS7(1)
2
3
4
6 pkcs7 - PKCS#7 utility
7
9 openssl pkcs7 [-inform PEM|DER] [-outform PEM|DER] [-in filename] [-out
10 filename] [-print_certs] [-text] [-noout] [-engine id]
11
13 The pkcs7 command processes PKCS#7 files in DER or PEM format.
14
16 -inform DER|PEM
17 This specifies the input format. DER format is DER encoded PKCS#7
18 v1.5 structure.PEM (the default) is a base64 encoded version of the
19 DER form with header and footer lines.
20
21 -outform DER|PEM
22 This specifies the output format, the options have the same meaning
23 as the -inform option.
24
25 -in filename
26 This specifies the input filename to read from or standard input if
27 this option is not specified.
28
29 -out filename
30 specifies the output filename to write to or standard output by
31 default.
32
33 -print_certs
34 prints out any certificates or CRLs contained in the file. They are
35 preceded by their subject and issuer names in one line format.
36
37 -text
38 prints out certificates details in full rather than just subject
39 and issuer names.
40
41 -noout
42 don't output the encoded version of the PKCS#7 structure (or
43 certificates is -print_certs is set).
44
45 -engine id
46 specifying an engine (by its unique id string) will cause pkcs7 to
47 attempt to obtain a functional reference to the specified engine,
48 thus initialising it if needed. The engine will then be set as the
49 default for all available algorithms.
50
52 Convert a PKCS#7 file from PEM to DER:
53
54 openssl pkcs7 -in file.pem -outform DER -out file.der
55
56 Output all certificates in a file:
57
58 openssl pkcs7 -in file.pem -print_certs -out certs.pem
59
61 The PEM PKCS#7 format uses the header and footer lines:
62
63 -----BEGIN PKCS7-----
64 -----END PKCS7-----
65
66 For compatibility with some CAs it will also accept:
67
68 -----BEGIN CERTIFICATE-----
69 -----END CERTIFICATE-----
70
72 There is no option to print out all the fields of a PKCS#7 file.
73
74 This PKCS#7 routines only understand PKCS#7 v 1.5 as specified in
75 RFC2315 they cannot currently parse, for example, the new CMS as
76 described in RFC2630.
77
79 crl2pkcs7(1)
80
81
82
831.0.0e 2009-04-10 PKCS7(1)