6 spkac - SPKAC printing and generating utility
15 [B<-keyform PEM|DER|ENGINE>]
17 [B<-challenge string>]
27 The B<spkac> command processes Netscape signed public key and challenge
28 (SPKAC) files. It can print out their contents, verify the signature and
29 produce its own SPKACs from a supplied private key.
37 Print out a usage message.
41 This specifies the input filename to read from or standard input if this
42 option is not specified. Ignored if the B<-key> option is used.
44 =item B<-out filename>
46 Specifies the output filename to write to or standard output by
51 Create an SPKAC file using the private key in B<keyfile>. The
52 B<-in>, B<-noout>, B<-spksect> and B<-verify> options are ignored if
55 =item B<-keyform PEM|DER|ENGINE>
57 Whether the key format is PEM, DER, or an engine-backed key.
60 =item B<-passin password>
62 The input file password source. For more information about the format of B<arg>
63 see the B<PASS PHRASE ARGUMENTS> section in L<openssl(1)>.
65 =item B<-challenge string>
67 Specifies the challenge string if an SPKAC is being created.
69 =item B<-spkac spkacname>
71 Allows an alternative name form the variable containing the
72 SPKAC. The default is "SPKAC". This option affects both
73 generated and input SPKAC files.
75 =item B<-spksect section>
77 Allows an alternative name form the section containing the
78 SPKAC. The default is the default section.
82 Don't output the text version of the SPKAC (not used if an
83 SPKAC is being created).
87 Output the public key of an SPKAC (not used if an SPKAC is
92 Verifies the digital signature on the supplied SPKAC.
96 Specifying an engine (by its unique B<id> string) will cause B<spkac>
97 to attempt to obtain a functional reference to the specified engine,
98 thus initialising it if needed. The engine will then be set as the default
99 for all available algorithms.
105 Print out the contents of an SPKAC:
107 openssl spkac -in spkac.cnf
109 Verify the signature of an SPKAC:
111 openssl spkac -in spkac.cnf -noout -verify
113 Create an SPKAC using the challenge string "hello":
115 openssl spkac -key key.pem -challenge hello -out spkac.cnf
117 Example of an SPKAC, (long lines split up for clarity):
119 SPKAC=MIG5MGUwXDANBgkqhkiG9w0BAQEFAANLADBIAkEA1cCoq2Wa3Ixs47uI7F\
120 PVwHVIPDx5yso105Y6zpozam135a8R0CpoRvkkigIyXfcCjiVi5oWk+6FfPaD03u\
121 PFoQIDAQABFgVoZWxsbzANBgkqhkiG9w0BAQQFAANBAFpQtY/FojdwkJh1bEIYuc\
122 2EeM2KHTWPEepWYeawvHD0gQ3DngSC75YCWnnDdq+NQ3F+X4deMx9AaEglZtULwV\
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".
147 Copyright 2000-2017 The OpenSSL Project Authors. All Rights Reserved.
149 Licensed under the OpenSSL license (the "License"). You may not use
150 this file except in compliance with the License. You can obtain a copy
151 in the file LICENSE in the source distribution or at
152 L<https://www.openssl.org/source/license.html>.