1SPKAC(1) OpenSSL SPKAC(1)
2
3
4
6 spkac - SPKAC printing and generating utility
7
9 openssl spkac [-in filename] [-out filename] [-key keyfile] [-passin
10 arg] [-challenge string] [-pubkey] [-spkac spkacname] [-spksect
11 section] [-noout] [-verify] [-engine id]
12
14 The spkac command processes Netscape signed public key and challenge
15 (SPKAC) files. It can print out their contents, verify the signature
16 and produce its own SPKACs from a supplied private key.
17
19 -in filename
20 This specifies the input filename to read from or standard input if
21 this option is not specified. Ignored if the -key option is used.
22
23 -out filename
24 specifies the output filename to write to or standard output by
25 default.
26
27 -key keyfile
28 create an SPKAC file using the private key in keyfile. The -in,
29 -noout, -spksect and -verify options are ignored if present.
30
31 -passin password
32 the input file password source. For more information about the
33 format of arg see the PASS PHRASE ARGUMENTS section in openssl(1).
34
35 -challenge string
36 specifies the challenge string if an SPKAC is being created.
37
38 -spkac spkacname
39 allows an alternative name form the variable containing the SPKAC.
40 The default is "SPKAC". This option affects both generated and
41 input SPKAC files.
42
43 -spksect section
44 allows an alternative name form the section containing the SPKAC.
45 The default is the default section.
46
47 -noout
48 don't output the text version of the SPKAC (not used if an SPKAC is
49 being created).
50
51 -pubkey
52 output the public key of an SPKAC (not used if an SPKAC is being
53 created).
54
55 -verify
56 verifies the digital signature on the supplied SPKAC.
57
58 -engine id
59 specifying an engine (by its unique id string) will cause spkac to
60 attempt to obtain a functional reference to the specified engine,
61 thus initialising it if needed. The engine will then be set as the
62 default for all available algorithms.
63
65 Print out the contents of an SPKAC:
66
67 openssl spkac -in spkac.cnf
68
69 Verify the signature of an SPKAC:
70
71 openssl spkac -in spkac.cnf -noout -verify
72
73 Create an SPKAC using the challenge string "hello":
74
75 openssl spkac -key key.pem -challenge hello -out spkac.cnf
76
77 Example of an SPKAC, (long lines split up for clarity):
78
79 SPKAC=MIG5MGUwXDANBgkqhkiG9w0BAQEFAANLADBIAkEA1cCoq2Wa3Ixs47uI7F\
80 PVwHVIPDx5yso105Y6zpozam135a8R0CpoRvkkigIyXfcCjiVi5oWk+6FfPaD03u\
81 PFoQIDAQABFgVoZWxsbzANBgkqhkiG9w0BAQQFAANBAFpQtY/FojdwkJh1bEIYuc\
82 2EeM2KHTWPEepWYeawvHD0gQ3DngSC75YCWnnDdq+NQ3F+X4deMx9AaEglZtULwV\
83 4=
84
86 A created SPKAC with suitable DN components appended can be fed into
87 the ca utility.
88
89 SPKACs are typically generated by Netscape when a form is submitted
90 containing the KEYGEN tag as part of the certificate enrollment
91 process.
92
93 The challenge string permits a primitive form of proof of possession of
94 private key. By checking the SPKAC signature and a random challenge
95 string some guarantee is given that the user knows the private key
96 corresponding to the public key being certified. This is important in
97 some applications. Without this it is possible for a previous SPKAC to
98 be used in a "replay attack".
99
101 ca(1)
102
103
104
1051.0.0e 2009-04-10 SPKAC(1)