5 openssl-spkac - SPKAC printing and generating utility
14 [B<-keyform PEM|DER|ENGINE>]
16 [B<-challenge string>]
26 The B<spkac> command processes Netscape signed public key and challenge
27 (SPKAC) files. It can print out their contents, verify the signature and
28 produce its own SPKACs from a supplied private key.
36 Print out a usage message.
40 This specifies the input filename to read from or standard input if this
41 option is not specified. Ignored if the B<-key> option is used.
43 =item B<-out filename>
45 Specifies the output filename to write to or standard output by
50 Create an SPKAC file using the private key in B<keyfile>. The
51 B<-in>, B<-noout>, B<-spksect> and B<-verify> options are ignored if
54 =item B<-keyform PEM|DER|ENGINE>
56 Whether the key format is PEM, DER, or an engine-backed key.
59 =item B<-passin password>
61 The input file password source. For more information about the format of B<arg>
62 see the B<PASS PHRASE ARGUMENTS> section in L<openssl(1)>.
64 =item B<-challenge string>
66 Specifies the challenge string if an SPKAC is being created.
68 =item B<-spkac spkacname>
70 Allows an alternative name form the variable containing the
71 SPKAC. The default is "SPKAC". This option affects both
72 generated and input SPKAC files.
74 =item B<-spksect section>
76 Allows an alternative name form the section containing the
77 SPKAC. The default is the default section.
81 Don't output the text version of the SPKAC (not used if an
82 SPKAC is being created).
86 Output the public key of an SPKAC (not used if an SPKAC is
91 Verifies the digital signature on the supplied SPKAC.
95 Specifying an engine (by its unique B<id> string) will cause B<spkac>
96 to attempt to obtain a functional reference to the specified engine,
97 thus initialising it if needed. The engine will then be set as the default
98 for all available algorithms.
104 Print out the contents of an SPKAC:
106 openssl spkac -in spkac.cnf
108 Verify the signature of an SPKAC:
110 openssl spkac -in spkac.cnf -noout -verify
112 Create an SPKAC using the challenge string "hello":
114 openssl spkac -key key.pem -challenge hello -out spkac.cnf
116 Example of an SPKAC, (long lines split up for clarity):
118 SPKAC=MIG5MGUwXDANBgkqhkiG9w0BAQEFAANLADBIAkEA\
119 1cCoq2Wa3Ixs47uI7FPVwHVIPDx5yso105Y6zpozam135a\
120 8R0CpoRvkkigIyXfcCjiVi5oWk+6FfPaD03uPFoQIDAQAB\
121 FgVoZWxsbzANBgkqhkiG9w0BAQQFAANBAFpQtY/FojdwkJ\
122 h1bEIYuc2EeM2KHTWPEepWYeawvHD0gQ3DngSC75YCWnnD\
123 dq+NQ3F+X4deMx9AaEglZtULwV4=
127 A created SPKAC with suitable DN components appended can be fed into
130 SPKACs are typically generated by Netscape when a form is submitted
131 containing the B<KEYGEN> tag as part of the certificate enrollment
134 The challenge string permits a primitive form of proof of possession
135 of private key. By checking the SPKAC signature and a random challenge
136 string some guarantee is given that the user knows the private key
137 corresponding to the public key being certified. This is important in
138 some applications. Without this it is possible for a previous SPKAC
139 to be used in a "replay attack".
148 Copyright 2000-2019 The OpenSSL Project Authors. All Rights Reserved.
150 Licensed under the Apache License 2.0 (the "License"). You may not use
151 this file except in compliance with the License. You can obtain a copy
152 in the file LICENSE in the source distribution or at
153 L<https://www.openssl.org/source/license.html>.