1 .\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.32
4 .\" ========================================================================
5 .de Sh \" Subsection heading
13 .de Sp \" Vertical space (when we can't use .PP)
17 .de Vb \" Begin verbatim text
22 .de Ve \" End verbatim text
26 .\" Set up some character translations and predefined strings. \*(-- will
27 .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
28 .\" double quote, and \*(R" will give a right double quote. | will give a
29 .\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
30 .\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
31 .\" expand to `' in nroff, nothing in troff, for use with C<>.
33 .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
37 . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
38 . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
51 .\" If the F register is turned on, we'll generate index entries on stderr for
52 .\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
53 .\" entries marked with X<> in POD. Of course, you'll have to process the
54 .\" output yourself in some meaningful fashion.
57 . tm Index:\\$1\t\\n%\t"\\$2"
63 .\" For nroff, turn off justification. Always turn off hyphenation; it makes
64 .\" way too many mistakes in technical documents.
68 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
69 .\" Fear. Run. Save yourself. No user-serviceable parts.
70 . \" fudge factors for nroff and troff
79 . ds #H ((1u-(\\\\n(.fu%2u))*.13m)
85 . \" simple accents for nroff and troff
95 . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
96 . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
97 . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
98 . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
99 . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
100 . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
102 . \" troff and (daisy-wheel) nroff accents
103 .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
104 .ds 8 \h'\*(#H'\(*b\h'-\*(#H'
105 .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
106 .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
107 .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
108 .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
109 .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
110 .ds ae a\h'-(\w'a'u*4/10)'e
111 .ds Ae A\h'-(\w'A'u*4/10)'E
112 . \" corrections for vroff
113 .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
114 .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
115 . \" for low resolution devices (crt and lpr)
116 .if \n(.H>23 .if \n(.V>19 \
129 .\" ========================================================================
132 .TH REQ 1 "2008-09-27" "0.9.8i" "OpenSSL"
134 req \- PKCS#10 certificate request and certificate generating utility.
136 .IX Header "SYNOPSIS"
137 \&\fBopenssl\fR \fBreq\fR
138 [\fB\-inform PEM|DER\fR]
139 [\fB\-outform PEM|DER\fR]
140 [\fB\-in filename\fR]
142 [\fB\-out filename\fR]
143 [\fB\-passout arg\fR]
150 [\fB\-rand file(s)\fR]
151 [\fB\-newkey rsa:bits\fR]
152 [\fB\-newkey dsa:file\fR]
154 [\fB\-key filename\fR]
155 [\fB\-keyform PEM|DER\fR]
156 [\fB\-keyout filename\fR]
157 [\fB\-[md5|sha1|md2|mdc2]\fR]
158 [\fB\-config filename\fR]
160 [\fB\-multivalue\-rdn\fR]
163 [\fB\-set_serial n\fR]
164 [\fB\-asn1\-kludge\fR]
166 [\fB\-extensions section\fR]
167 [\fB\-reqexts section\fR]
174 .IX Header "DESCRIPTION"
175 The \fBreq\fR command primarily creates and processes certificate requests
176 in PKCS#10 format. It can additionally create self signed certificates
177 for use as root CAs for example.
178 .SH "COMMAND OPTIONS"
179 .IX Header "COMMAND OPTIONS"
180 .IP "\fB\-inform DER|PEM\fR" 4
181 .IX Item "-inform DER|PEM"
182 This specifies the input format. The \fB\s-1DER\s0\fR option uses an \s-1ASN1\s0 \s-1DER\s0 encoded
183 form compatible with the PKCS#10. The \fB\s-1PEM\s0\fR form is the default format: it
184 consists of the \fB\s-1DER\s0\fR format base64 encoded with additional header and
186 .IP "\fB\-outform DER|PEM\fR" 4
187 .IX Item "-outform DER|PEM"
188 This specifies the output format, the options have the same meaning as the
189 \&\fB\-inform\fR option.
190 .IP "\fB\-in filename\fR" 4
191 .IX Item "-in filename"
192 This specifies the input filename to read a request from or standard input
193 if this option is not specified. A request is only read if the creation
194 options (\fB\-new\fR and \fB\-newkey\fR) are not specified.
195 .IP "\fB\-passin arg\fR" 4
196 .IX Item "-passin arg"
197 the input file password source. For more information about the format of \fBarg\fR
198 see the \fB\s-1PASS\s0 \s-1PHRASE\s0 \s-1ARGUMENTS\s0\fR section in \fIopenssl\fR\|(1).
199 .IP "\fB\-out filename\fR" 4
200 .IX Item "-out filename"
201 This specifies the output filename to write to or standard output by
203 .IP "\fB\-passout arg\fR" 4
204 .IX Item "-passout arg"
205 the output file password source. For more information about the format of \fBarg\fR
206 see the \fB\s-1PASS\s0 \s-1PHRASE\s0 \s-1ARGUMENTS\s0\fR section in \fIopenssl\fR\|(1).
209 prints out the certificate request in text form.
210 .IP "\fB\-pubkey\fR" 4
212 outputs the public key.
213 .IP "\fB\-noout\fR" 4
215 this option prevents output of the encoded version of the request.
216 .IP "\fB\-modulus\fR" 4
218 this option prints out the value of the modulus of the public key
219 contained in the request.
220 .IP "\fB\-verify\fR" 4
222 verifies the signature on the request.
225 this option generates a new certificate request. It will prompt
226 the user for the relevant field values. The actual fields
227 prompted for and their maximum and minimum sizes are specified
228 in the configuration file and any requested extensions.
230 If the \fB\-key\fR option is not used it will generate a new \s-1RSA\s0 private
231 key using information specified in the configuration file.
232 .IP "\fB\-rand file(s)\fR" 4
233 .IX Item "-rand file(s)"
234 a file or files containing random data used to seed the random number
235 generator, or an \s-1EGD\s0 socket (see \fIRAND_egd\fR\|(3)).
236 Multiple files can be specified separated by a OS-dependent character.
237 The separator is \fB;\fR for MS\-Windows, \fB,\fR for OpenVMS, and \fB:\fR for
239 .IP "\fB\-newkey arg\fR" 4
240 .IX Item "-newkey arg"
241 this option creates a new certificate request and a new private
242 key. The argument takes one of two forms. \fBrsa:nbits\fR, where
243 \&\fBnbits\fR is the number of bits, generates an \s-1RSA\s0 key \fBnbits\fR
244 in size. \fBdsa:filename\fR generates a \s-1DSA\s0 key using the parameters
245 in the file \fBfilename\fR.
246 .IP "\fB\-key filename\fR" 4
247 .IX Item "-key filename"
248 This specifies the file to read the private key from. It also
249 accepts PKCS#8 format private keys for \s-1PEM\s0 format files.
250 .IP "\fB\-keyform PEM|DER\fR" 4
251 .IX Item "-keyform PEM|DER"
252 the format of the private key file specified in the \fB\-key\fR
253 argument. \s-1PEM\s0 is the default.
254 .IP "\fB\-keyout filename\fR" 4
255 .IX Item "-keyout filename"
256 this gives the filename to write the newly created private key to.
257 If this option is not specified then the filename present in the
258 configuration file is used.
259 .IP "\fB\-nodes\fR" 4
261 if this option is specified then if a private key is created it
262 will not be encrypted.
263 .IP "\fB\-[md5|sha1|md2|mdc2]\fR" 4
264 .IX Item "-[md5|sha1|md2|mdc2]"
265 this specifies the message digest to sign the request with. This
266 overrides the digest algorithm specified in the configuration file.
267 This option is ignored for \s-1DSA\s0 requests: they always use \s-1SHA1\s0.
268 .IP "\fB\-config filename\fR" 4
269 .IX Item "-config filename"
270 this allows an alternative configuration file to be specified,
271 this overrides the compile time filename or any specified in
272 the \fB\s-1OPENSSL_CONF\s0\fR environment variable.
273 .IP "\fB\-subj arg\fR" 4
275 sets subject name for new request or supersedes the subject name
276 when processing a request.
277 The arg must be formatted as \fI/type0=value0/type1=value1/type2=...\fR,
278 characters may be escaped by \e (backslash), no spaces are skipped.
279 .IP "\fB\-multivalue\-rdn\fR" 4
280 .IX Item "-multivalue-rdn"
281 this option causes the \-subj argument to be interpreted with full
282 support for multivalued RDNs. Example:
284 \&\fI/DC=org/DC=OpenSSL/DC=users/UID=123456+CN=John Doe\fR
286 If \-multi\-rdn is not used then the \s-1UID\s0 value is \fI123456+CN=John Doe\fR.
289 this option outputs a self signed certificate instead of a certificate
290 request. This is typically used to generate a test certificate or
291 a self signed root \s-1CA\s0. The extensions added to the certificate
292 (if any) are specified in the configuration file. Unless specified
293 using the \fBset_serial\fR option \fB0\fR will be used for the serial
295 .IP "\fB\-days n\fR" 4
297 when the \fB\-x509\fR option is being used this specifies the number of
298 days to certify the certificate for. The default is 30 days.
299 .IP "\fB\-set_serial n\fR" 4
300 .IX Item "-set_serial n"
301 serial number to use when outputting a self signed certificate. This
302 may be specified as a decimal value or a hex value if preceded by \fB0x\fR.
303 It is possible to use negative serial numbers but this is not recommended.
304 .IP "\fB\-extensions section\fR" 4
305 .IX Item "-extensions section"
307 .IP "\fB\-reqexts section\fR" 4
308 .IX Item "-reqexts section"
310 these options specify alternative sections to include certificate
311 extensions (if the \fB\-x509\fR option is present) or certificate
312 request extensions. This allows several different sections to
313 be used in the same configuration file to specify requests for
314 a variety of purposes.
317 this option causes field values to be interpreted as \s-1UTF8\s0 strings, by
318 default they are interpreted as \s-1ASCII\s0. This means that the field
319 values, whether prompted from a terminal or obtained from a
320 configuration file, must be valid \s-1UTF8\s0 strings.
321 .IP "\fB\-nameopt option\fR" 4
322 .IX Item "-nameopt option"
323 option which determines how the subject or issuer names are displayed. The
324 \&\fBoption\fR argument can be a single option or multiple options separated by
325 commas. Alternatively the \fB\-nameopt\fR switch may be used more than once to
326 set multiple options. See the \fIx509\fR\|(1) manual page for details.
327 .IP "\fB\-asn1\-kludge\fR" 4
328 .IX Item "-asn1-kludge"
329 by default the \fBreq\fR command outputs certificate requests containing
330 no attributes in the correct PKCS#10 format. However certain CAs will only
331 accept requests containing no attributes in an invalid form: this
332 option produces this invalid format.
334 More precisely the \fBAttributes\fR in a PKCS#10 certificate request
335 are defined as a \fB\s-1SET\s0 \s-1OF\s0 Attribute\fR. They are \fBnot \s-1OPTIONAL\s0\fR so
336 if no attributes are present then they should be encoded as an
337 empty \fB\s-1SET\s0 \s-1OF\s0\fR. The invalid form does not include the empty
338 \&\fB\s-1SET\s0 \s-1OF\s0\fR whereas the correct form does.
340 It should be noted that very few CAs still require the use of this option.
341 .IP "\fB\-newhdr\fR" 4
343 Adds the word \fB\s-1NEW\s0\fR to the \s-1PEM\s0 file header and footer lines on the outputed
344 request. Some software (Netscape certificate server) and some CAs need this.
345 .IP "\fB\-batch\fR" 4
347 non-interactive mode.
348 .IP "\fB\-verbose\fR" 4
350 print extra details about the operations being performed.
351 .IP "\fB\-engine id\fR" 4
352 .IX Item "-engine id"
353 specifying an engine (by it's unique \fBid\fR string) will cause \fBreq\fR
354 to attempt to obtain a functional reference to the specified engine,
355 thus initialising it if needed. The engine will then be set as the default
356 for all available algorithms.
357 .SH "CONFIGURATION FILE FORMAT"
358 .IX Header "CONFIGURATION FILE FORMAT"
359 The configuration options are specified in the \fBreq\fR section of
360 the configuration file. As with all configuration files if no
361 value is specified in the specific section (i.e. \fBreq\fR) then
362 the initial unnamed or \fBdefault\fR section is searched too.
364 The options available are described in detail below.
365 .IP "\fBinput_password output_password\fR" 4
366 .IX Item "input_password output_password"
367 The passwords for the input private key file (if present) and
368 the output private key file (if one will be created). The
369 command line options \fBpassin\fR and \fBpassout\fR override the
370 configuration file values.
371 .IP "\fBdefault_bits\fR" 4
372 .IX Item "default_bits"
373 This specifies the default key size in bits. If not specified then
374 512 is used. It is used if the \fB\-new\fR option is used. It can be
375 overridden by using the \fB\-newkey\fR option.
376 .IP "\fBdefault_keyfile\fR" 4
377 .IX Item "default_keyfile"
378 This is the default filename to write a private key to. If not
379 specified the key is written to standard output. This can be
380 overridden by the \fB\-keyout\fR option.
381 .IP "\fBoid_file\fR" 4
383 This specifies a file containing additional \fB\s-1OBJECT\s0 \s-1IDENTIFIERS\s0\fR.
384 Each line of the file should consist of the numerical form of the
385 object identifier followed by white space then the short name followed
386 by white space and finally the long name.
387 .IP "\fBoid_section\fR" 4
388 .IX Item "oid_section"
389 This specifies a section in the configuration file containing extra
390 object identifiers. Each line should consist of the short name of the
391 object identifier followed by \fB=\fR and the numerical form. The short
392 and long names are the same when this option is used.
393 .IP "\fB\s-1RANDFILE\s0\fR" 4
395 This specifies a filename in which random number seed information is
396 placed and read from, or an \s-1EGD\s0 socket (see \fIRAND_egd\fR\|(3)).
397 It is used for private key generation.
398 .IP "\fBencrypt_key\fR" 4
399 .IX Item "encrypt_key"
400 If this is set to \fBno\fR then if a private key is generated it is
401 \&\fBnot\fR encrypted. This is equivalent to the \fB\-nodes\fR command line
402 option. For compatibility \fBencrypt_rsa_key\fR is an equivalent option.
403 .IP "\fBdefault_md\fR" 4
404 .IX Item "default_md"
405 This option specifies the digest algorithm to use. Possible values
406 include \fBmd5 sha1 mdc2\fR. If not present then \s-1MD5\s0 is used. This
407 option can be overridden on the command line.
408 .IP "\fBstring_mask\fR" 4
409 .IX Item "string_mask"
410 This option masks out the use of certain string types in certain
411 fields. Most users will not need to change this option.
413 It can be set to several values \fBdefault\fR which is also the default
414 option uses PrintableStrings, T61Strings and BMPStrings if the
415 \&\fBpkix\fR value is used then only PrintableStrings and BMPStrings will
416 be used. This follows the \s-1PKIX\s0 recommendation in \s-1RFC2459\s0. If the
417 \&\fButf8only\fR option is used then only UTF8Strings will be used: this
418 is the \s-1PKIX\s0 recommendation in \s-1RFC2459\s0 after 2003. Finally the \fBnombstr\fR
419 option just uses PrintableStrings and T61Strings: certain software has
420 problems with BMPStrings and UTF8Strings: in particular Netscape.
421 .IP "\fBreq_extensions\fR" 4
422 .IX Item "req_extensions"
423 this specifies the configuration file section containing a list of
424 extensions to add to the certificate request. It can be overridden
425 by the \fB\-reqexts\fR command line switch.
426 .IP "\fBx509_extensions\fR" 4
427 .IX Item "x509_extensions"
428 this specifies the configuration file section containing a list of
429 extensions to add to certificate generated when the \fB\-x509\fR switch
430 is used. It can be overridden by the \fB\-extensions\fR command line switch.
433 if set to the value \fBno\fR this disables prompting of certificate fields
434 and just takes values from the config file directly. It also changes the
435 expected format of the \fBdistinguished_name\fR and \fBattributes\fR sections.
438 if set to the value \fByes\fR then field values to be interpreted as \s-1UTF8\s0
439 strings, by default they are interpreted as \s-1ASCII\s0. This means that
440 the field values, whether prompted from a terminal or obtained from a
441 configuration file, must be valid \s-1UTF8\s0 strings.
442 .IP "\fBattributes\fR" 4
443 .IX Item "attributes"
444 this specifies the section containing any request attributes: its format
445 is the same as \fBdistinguished_name\fR. Typically these may contain the
446 challengePassword or unstructuredName types. They are currently ignored
447 by OpenSSL's request signing utilities but some CAs might want them.
448 .IP "\fBdistinguished_name\fR" 4
449 .IX Item "distinguished_name"
450 This specifies the section containing the distinguished name fields to
451 prompt for when generating a certificate or certificate request. The format
452 is described in the next section.
453 .SH "DISTINGUISHED NAME AND ATTRIBUTE SECTION FORMAT"
454 .IX Header "DISTINGUISHED NAME AND ATTRIBUTE SECTION FORMAT"
455 There are two separate formats for the distinguished name and attribute
456 sections. If the \fBprompt\fR option is set to \fBno\fR then these sections
457 just consist of field names and values: for example,
461 \& OU=My Organization
462 \& emailAddress=someone@somewhere.org
465 This allows external programs (e.g. \s-1GUI\s0 based) to generate a template file
466 with all the field names and values and just pass it to \fBreq\fR. An example
467 of this kind of configuration file is contained in the \fB\s-1EXAMPLES\s0\fR section.
469 Alternatively if the \fBprompt\fR option is absent or not set to \fBno\fR then the
470 file contains field prompting information. It consists of lines of the form:
473 \& fieldName="prompt"
474 \& fieldName_default="default field value"
479 \&\*(L"fieldName\*(R" is the field name being used, for example commonName (or \s-1CN\s0).
480 The \*(L"prompt\*(R" string is used to ask the user to enter the relevant
481 details. If the user enters nothing then the default value is used if no
482 default value is present then the field is omitted. A field can
483 still be omitted if a default value is present if the user just
484 enters the '.' character.
486 The number of characters entered must be between the fieldName_min and
487 fieldName_max limits: there may be additional restrictions based
488 on the field being used (for example countryName can only ever be
489 two characters long and must fit in a PrintableString).
491 Some fields (such as organizationName) can be used more than once
492 in a \s-1DN\s0. This presents a problem because configuration files will
493 not recognize the same name occurring twice. To avoid this problem
494 if the fieldName contains some characters followed by a full stop
495 they will be ignored. So for example a second organizationName can
496 be input by calling it \*(L"1.organizationName\*(R".
498 The actual permitted field names are any object identifier short or
499 long names. These are compiled into OpenSSL and include the usual
500 values such as commonName, countryName, localityName, organizationName,
501 organizationUnitName, stateOrProvinceName. Additionally emailAddress
502 is include as well as name, surname, givenName initials and dnQualifier.
504 Additional object identifiers can be defined with the \fBoid_file\fR or
505 \&\fBoid_section\fR options in the configuration file. Any additional fields
506 will be treated as though they were a DirectoryString.
508 .IX Header "EXAMPLES"
509 Examine and verify certificate request:
512 \& openssl req -in req.pem -text -verify -noout
515 Create a private key and then generate a certificate request from it:
518 \& openssl genrsa -out key.pem 1024
519 \& openssl req -new -key key.pem -out req.pem
522 The same but just using req:
525 \& openssl req -newkey rsa:1024 -keyout key.pem -out req.pem
528 Generate a self signed root certificate:
531 \& openssl req -x509 -newkey rsa:1024 -keyout key.pem -out req.pem
534 Example of a file pointed to by the \fBoid_file\fR option:
537 \& 1.2.3.4 shortName A longer Name
538 \& 1.2.3.6 otherName Other longer Name
541 Example of a section pointed to by \fBoid_section\fR making use of variable
546 \& testoid2=${testoid1}.6
549 Sample configuration file prompting for field values:
553 \& default_bits = 1024
554 \& default_keyfile = privkey.pem
555 \& distinguished_name = req_distinguished_name
556 \& attributes = req_attributes
557 \& x509_extensions = v3_ca
561 \& dirstring_type = nobmp
565 \& [ req_distinguished_name ]
566 \& countryName = Country Name (2 letter code)
567 \& countryName_default = AU
568 \& countryName_min = 2
569 \& countryName_max = 2
573 \& localityName = Locality Name (eg, city)
577 \& organizationalUnitName = Organizational Unit Name (eg, section)
581 \& commonName = Common Name (eg, YOUR name)
582 \& commonName_max = 64
586 \& emailAddress = Email Address
587 \& emailAddress_max = 40
591 \& [ req_attributes ]
592 \& challengePassword = A challenge password
593 \& challengePassword_min = 4
594 \& challengePassword_max = 20
602 \& subjectKeyIdentifier=hash
603 \& authorityKeyIdentifier=keyid:always,issuer:always
604 \& basicConstraints = CA:true
607 Sample configuration containing all field values:
610 \& RANDFILE = $ENV::HOME/.rnd
615 \& default_bits = 1024
616 \& default_keyfile = keyfile.pem
617 \& distinguished_name = req_distinguished_name
618 \& attributes = req_attributes
620 \& output_password = mypass
624 \& [ req_distinguished_name ]
626 \& ST = Test State or Province
628 \& O = Organization Name
629 \& OU = Organizational Unit Name
631 \& emailAddress = test@email.address
635 \& [ req_attributes ]
636 \& challengePassword = A challenge password
640 The header and footer lines in the \fB\s-1PEM\s0\fR format are normally:
643 \& -----BEGIN CERTIFICATE REQUEST-----
644 \& -----END CERTIFICATE REQUEST-----
647 some software (some versions of Netscape certificate server) instead needs:
650 \& -----BEGIN NEW CERTIFICATE REQUEST-----
651 \& -----END NEW CERTIFICATE REQUEST-----
654 which is produced with the \fB\-newhdr\fR option but is otherwise compatible.
655 Either form is accepted transparently on input.
657 The certificate requests generated by \fBXenroll\fR with \s-1MSIE\s0 have extensions
658 added. It includes the \fBkeyUsage\fR extension which determines the type of
659 key (signature only or general purpose) and any additional OIDs entered
660 by the script in an extendedKeyUsage extension.
662 .IX Header "DIAGNOSTICS"
663 The following messages are frequently asked about:
666 \& Using configuration from /some/path/openssl.cnf
667 \& Unable to load config info
670 This is followed some time later by...
673 \& unable to find 'distinguished_name' in config
674 \& problems making Certificate Request
677 The first error message is the clue: it can't find the configuration
678 file! Certain operations (like examining a certificate request) don't
679 need a configuration file so its use isn't enforced. Generation of
680 certificates or requests however does need a configuration file. This
681 could be regarded as a bug.
683 Another puzzling message is this:
690 this is displayed when no attributes are present and the request includes
691 the correct empty \fB\s-1SET\s0 \s-1OF\s0\fR structure (the \s-1DER\s0 encoding of which is 0xa0
692 0x00). If you just see:
698 then the \fB\s-1SET\s0 \s-1OF\s0\fR is missing and the encoding is technically invalid (but
699 it is tolerated). See the description of the command line option \fB\-asn1\-kludge\fR
700 for more information.
701 .SH "ENVIRONMENT VARIABLES"
702 .IX Header "ENVIRONMENT VARIABLES"
703 The variable \fB\s-1OPENSSL_CONF\s0\fR if defined allows an alternative configuration
704 file location to be specified, it will be overridden by the \fB\-config\fR command
705 line switch if it is present. For compatibility reasons the \fB\s-1SSLEAY_CONF\s0\fR
706 environment variable serves the same purpose but its use is discouraged.
709 OpenSSL's handling of T61Strings (aka TeletexStrings) is broken: it effectively
710 treats them as \s-1ISO\-8859\-1\s0 (Latin 1), Netscape and \s-1MSIE\s0 have similar behaviour.
711 This can cause problems if you need characters that aren't available in
712 PrintableStrings and you don't want to or can't use BMPStrings.
714 As a consequence of the T61String handling the only correct way to represent
715 accented characters in OpenSSL is to use a BMPString: unfortunately Netscape
716 currently chokes on these. If you have to use accented characters with Netscape
717 and \s-1MSIE\s0 then you currently need to use the invalid T61String form.
719 The current prompting is not very friendly. It doesn't allow you to confirm what
720 you've just entered. Other things like extensions in certificate requests are
721 statically defined in the configuration file. Some of these: like an email
722 address in subjectAltName should be input by the user.
724 .IX Header "SEE ALSO"
725 \&\fIx509\fR\|(1), \fIca\fR\|(1), \fIgenrsa\fR\|(1),
726 \&\fIgendsa\fR\|(1), \fIconfig\fR\|(5)
nant's projects / dragonfly.git / blob