1 .\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
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 "2004-12-18" "0.9.7e" "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]
162 [\fB\-set_serial n\fR]
163 [\fB\-asn1\-kludge\fR]
165 [\fB\-extensions section\fR]
166 [\fB\-reqexts section\fR]
173 .IX Header "DESCRIPTION"
174 The \fBreq\fR command primarily creates and processes certificate requests
175 in PKCS#10 format. It can additionally create self signed certificates
176 for use as root CAs for example.
177 .SH "COMMAND OPTIONS"
178 .IX Header "COMMAND OPTIONS"
179 .IP "\fB\-inform DER|PEM\fR" 4
180 .IX Item "-inform DER|PEM"
181 This specifies the input format. The \fB\s-1DER\s0\fR option uses an \s-1ASN1\s0 \s-1DER\s0 encoded
182 form compatible with the PKCS#10. The \fB\s-1PEM\s0\fR form is the default format: it
183 consists of the \fB\s-1DER\s0\fR format base64 encoded with additional header and
185 .IP "\fB\-outform DER|PEM\fR" 4
186 .IX Item "-outform DER|PEM"
187 This specifies the output format, the options have the same meaning as the
188 \&\fB\-inform\fR option.
189 .IP "\fB\-in filename\fR" 4
190 .IX Item "-in filename"
191 This specifies the input filename to read a request from or standard input
192 if this option is not specified. A request is only read if the creation
193 options (\fB\-new\fR and \fB\-newkey\fR) are not specified.
194 .IP "\fB\-passin arg\fR" 4
195 .IX Item "-passin arg"
196 the input file password source. For more information about the format of \fBarg\fR
197 see the \fB\s-1PASS\s0 \s-1PHRASE\s0 \s-1ARGUMENTS\s0\fR section in \fIopenssl\fR\|(1).
198 .IP "\fB\-out filename\fR" 4
199 .IX Item "-out filename"
200 This specifies the output filename to write to or standard output by
202 .IP "\fB\-passout arg\fR" 4
203 .IX Item "-passout arg"
204 the output file password source. For more information about the format of \fBarg\fR
205 see the \fB\s-1PASS\s0 \s-1PHRASE\s0 \s-1ARGUMENTS\s0\fR section in \fIopenssl\fR\|(1).
208 prints out the certificate request in text form.
209 .IP "\fB\-pubkey\fR" 4
211 outputs the public key.
212 .IP "\fB\-noout\fR" 4
214 this option prevents output of the encoded version of the request.
215 .IP "\fB\-modulus\fR" 4
217 this option prints out the value of the modulus of the public key
218 contained in the request.
219 .IP "\fB\-verify\fR" 4
221 verifies the signature on the request.
224 this option generates a new certificate request. It will prompt
225 the user for the relevant field values. The actual fields
226 prompted for and their maximum and minimum sizes are specified
227 in the configuration file and any requested extensions.
229 If the \fB\-key\fR option is not used it will generate a new \s-1RSA\s0 private
230 key using information specified in the configuration file.
231 .IP "\fB\-rand file(s)\fR" 4
232 .IX Item "-rand file(s)"
233 a file or files containing random data used to seed the random number
234 generator, or an \s-1EGD\s0 socket (see \fIRAND_egd\fR\|(3)).
235 Multiple files can be specified separated by a OS-dependent character.
236 The separator is \fB;\fR for MS\-Windows, \fB,\fR for OpenVMS, and \fB:\fR for
238 .IP "\fB\-newkey arg\fR" 4
239 .IX Item "-newkey arg"
240 this option creates a new certificate request and a new private
241 key. The argument takes one of two forms. \fBrsa:nbits\fR, where
242 \&\fBnbits\fR is the number of bits, generates an \s-1RSA\s0 key \fBnbits\fR
243 in size. \fBdsa:filename\fR generates a \s-1DSA\s0 key using the parameters
244 in the file \fBfilename\fR.
245 .IP "\fB\-key filename\fR" 4
246 .IX Item "-key filename"
247 This specifies the file to read the private key from. It also
248 accepts PKCS#8 format private keys for \s-1PEM\s0 format files.
249 .IP "\fB\-keyform PEM|DER\fR" 4
250 .IX Item "-keyform PEM|DER"
251 the format of the private key file specified in the \fB\-key\fR
252 argument. \s-1PEM\s0 is the default.
253 .IP "\fB\-keyout filename\fR" 4
254 .IX Item "-keyout filename"
255 this gives the filename to write the newly created private key to.
256 If this option is not specified then the filename present in the
257 configuration file is used.
258 .IP "\fB\-nodes\fR" 4
260 if this option is specified then if a private key is created it
261 will not be encrypted.
262 .IP "\fB\-[md5|sha1|md2|mdc2]\fR" 4
263 .IX Item "-[md5|sha1|md2|mdc2]"
264 this specifies the message digest to sign the request with. This
265 overrides the digest algorithm specified in the configuration file.
266 This option is ignored for \s-1DSA\s0 requests: they always use \s-1SHA1\s0.
267 .IP "\fB\-config filename\fR" 4
268 .IX Item "-config filename"
269 this allows an alternative configuration file to be specified,
270 this overrides the compile time filename or any specified in
271 the \fB\s-1OPENSSL_CONF\s0\fR environment variable.
272 .IP "\fB\-subj arg\fR" 4
274 sets subject name for new request or supersedes the subject name
275 when processing a request.
276 The arg must be formatted as \fI/type0=value0/type1=value1/type2=...\fR,
277 characters may be escaped by \e (backslash), no spaces are skipped.
280 this option outputs a self signed certificate instead of a certificate
281 request. This is typically used to generate a test certificate or
282 a self signed root \s-1CA\s0. The extensions added to the certificate
283 (if any) are specified in the configuration file. Unless specified
284 using the \fBset_serial\fR option \fB0\fR will be used for the serial
286 .IP "\fB\-days n\fR" 4
288 when the \fB\-x509\fR option is being used this specifies the number of
289 days to certify the certificate for. The default is 30 days.
290 .IP "\fB\-set_serial n\fR" 4
291 .IX Item "-set_serial n"
292 serial number to use when outputting a self signed certificate. This
293 may be specified as a decimal value or a hex value if preceded by \fB0x\fR.
294 It is possible to use negative serial numbers but this is not recommended.
295 .IP "\fB\-extensions section\fR" 4
296 .IX Item "-extensions section"
298 .IP "\fB\-reqexts section\fR" 4
299 .IX Item "-reqexts section"
301 these options specify alternative sections to include certificate
302 extensions (if the \fB\-x509\fR option is present) or certificate
303 request extensions. This allows several different sections to
304 be used in the same configuration file to specify requests for
305 a variety of purposes.
308 this option causes field values to be interpreted as \s-1UTF8\s0 strings, by
309 default they are interpreted as \s-1ASCII\s0. This means that the field
310 values, whether prompted from a terminal or obtained from a
311 configuration file, must be valid \s-1UTF8\s0 strings.
312 .IP "\fB\-nameopt option\fR" 4
313 .IX Item "-nameopt option"
314 option which determines how the subject or issuer names are displayed. The
315 \&\fBoption\fR argument can be a single option or multiple options separated by
316 commas. Alternatively the \fB\-nameopt\fR switch may be used more than once to
317 set multiple options. See the \fIx509\fR\|(1) manual page for details.
318 .IP "\fB\-asn1\-kludge\fR" 4
319 .IX Item "-asn1-kludge"
320 by default the \fBreq\fR command outputs certificate requests containing
321 no attributes in the correct PKCS#10 format. However certain CAs will only
322 accept requests containing no attributes in an invalid form: this
323 option produces this invalid format.
325 More precisely the \fBAttributes\fR in a PKCS#10 certificate request
326 are defined as a \fB\s-1SET\s0 \s-1OF\s0 Attribute\fR. They are \fBnot \s-1OPTIONAL\s0\fR so
327 if no attributes are present then they should be encoded as an
328 empty \fB\s-1SET\s0 \s-1OF\s0\fR. The invalid form does not include the empty
329 \&\fB\s-1SET\s0 \s-1OF\s0\fR whereas the correct form does.
331 It should be noted that very few CAs still require the use of this option.
332 .IP "\fB\-newhdr\fR" 4
334 Adds the word \fB\s-1NEW\s0\fR to the \s-1PEM\s0 file header and footer lines on the outputed
335 request. Some software (Netscape certificate server) and some CAs need this.
336 .IP "\fB\-batch\fR" 4
338 non-interactive mode.
339 .IP "\fB\-verbose\fR" 4
341 print extra details about the operations being performed.
342 .IP "\fB\-engine id\fR" 4
343 .IX Item "-engine id"
344 specifying an engine (by it's unique \fBid\fR string) will cause \fBreq\fR
345 to attempt to obtain a functional reference to the specified engine,
346 thus initialising it if needed. The engine will then be set as the default
347 for all available algorithms.
348 .SH "CONFIGURATION FILE FORMAT"
349 .IX Header "CONFIGURATION FILE FORMAT"
350 The configuration options are specified in the \fBreq\fR section of
351 the configuration file. As with all configuration files if no
352 value is specified in the specific section (i.e. \fBreq\fR) then
353 the initial unnamed or \fBdefault\fR section is searched too.
355 The options available are described in detail below.
356 .IP "\fBinput_password output_password\fR" 4
357 .IX Item "input_password output_password"
358 The passwords for the input private key file (if present) and
359 the output private key file (if one will be created). The
360 command line options \fBpassin\fR and \fBpassout\fR override the
361 configuration file values.
362 .IP "\fBdefault_bits\fR" 4
363 .IX Item "default_bits"
364 This specifies the default key size in bits. If not specified then
365 512 is used. It is used if the \fB\-new\fR option is used. It can be
366 overridden by using the \fB\-newkey\fR option.
367 .IP "\fBdefault_keyfile\fR" 4
368 .IX Item "default_keyfile"
369 This is the default filename to write a private key to. If not
370 specified the key is written to standard output. This can be
371 overridden by the \fB\-keyout\fR option.
372 .IP "\fBoid_file\fR" 4
374 This specifies a file containing additional \fB\s-1OBJECT\s0 \s-1IDENTIFIERS\s0\fR.
375 Each line of the file should consist of the numerical form of the
376 object identifier followed by white space then the short name followed
377 by white space and finally the long name.
378 .IP "\fBoid_section\fR" 4
379 .IX Item "oid_section"
380 This specifies a section in the configuration file containing extra
381 object identifiers. Each line should consist of the short name of the
382 object identifier followed by \fB=\fR and the numerical form. The short
383 and long names are the same when this option is used.
384 .IP "\fB\s-1RANDFILE\s0\fR" 4
386 This specifies a filename in which random number seed information is
387 placed and read from, or an \s-1EGD\s0 socket (see \fIRAND_egd\fR\|(3)).
388 It is used for private key generation.
389 .IP "\fBencrypt_key\fR" 4
390 .IX Item "encrypt_key"
391 If this is set to \fBno\fR then if a private key is generated it is
392 \&\fBnot\fR encrypted. This is equivalent to the \fB\-nodes\fR command line
393 option. For compatibility \fBencrypt_rsa_key\fR is an equivalent option.
394 .IP "\fBdefault_md\fR" 4
395 .IX Item "default_md"
396 This option specifies the digest algorithm to use. Possible values
397 include \fBmd5 sha1 mdc2\fR. If not present then \s-1MD5\s0 is used. This
398 option can be overridden on the command line.
399 .IP "\fBstring_mask\fR" 4
400 .IX Item "string_mask"
401 This option masks out the use of certain string types in certain
402 fields. Most users will not need to change this option.
404 It can be set to several values \fBdefault\fR which is also the default
405 option uses PrintableStrings, T61Strings and BMPStrings if the
406 \&\fBpkix\fR value is used then only PrintableStrings and BMPStrings will
407 be used. This follows the \s-1PKIX\s0 recommendation in \s-1RFC2459\s0. If the
408 \&\fButf8only\fR option is used then only UTF8Strings will be used: this
409 is the \s-1PKIX\s0 recommendation in \s-1RFC2459\s0 after 2003. Finally the \fBnombstr\fR
410 option just uses PrintableStrings and T61Strings: certain software has
411 problems with BMPStrings and UTF8Strings: in particular Netscape.
412 .IP "\fBreq_extensions\fR" 4
413 .IX Item "req_extensions"
414 this specifies the configuration file section containing a list of
415 extensions to add to the certificate request. It can be overridden
416 by the \fB\-reqexts\fR command line switch.
417 .IP "\fBx509_extensions\fR" 4
418 .IX Item "x509_extensions"
419 this specifies the configuration file section containing a list of
420 extensions to add to certificate generated when the \fB\-x509\fR switch
421 is used. It can be overridden by the \fB\-extensions\fR command line switch.
424 if set to the value \fBno\fR this disables prompting of certificate fields
425 and just takes values from the config file directly. It also changes the
426 expected format of the \fBdistinguished_name\fR and \fBattributes\fR sections.
429 if set to the value \fByes\fR then field values to be interpreted as \s-1UTF8\s0
430 strings, by default they are interpreted as \s-1ASCII\s0. This means that
431 the field values, whether prompted from a terminal or obtained from a
432 configuration file, must be valid \s-1UTF8\s0 strings.
433 .IP "\fBattributes\fR" 4
434 .IX Item "attributes"
435 this specifies the section containing any request attributes: its format
436 is the same as \fBdistinguished_name\fR. Typically these may contain the
437 challengePassword or unstructuredName types. They are currently ignored
438 by OpenSSL's request signing utilities but some CAs might want them.
439 .IP "\fBdistinguished_name\fR" 4
440 .IX Item "distinguished_name"
441 This specifies the section containing the distinguished name fields to
442 prompt for when generating a certificate or certificate request. The format
443 is described in the next section.
444 .SH "DISTINGUISHED NAME AND ATTRIBUTE SECTION FORMAT"
445 .IX Header "DISTINGUISHED NAME AND ATTRIBUTE SECTION FORMAT"
446 There are two separate formats for the distinguished name and attribute
447 sections. If the \fBprompt\fR option is set to \fBno\fR then these sections
448 just consist of field names and values: for example,
452 \& OU=My Organization
453 \& emailAddress=someone@somewhere.org
456 This allows external programs (e.g. \s-1GUI\s0 based) to generate a template file
457 with all the field names and values and just pass it to \fBreq\fR. An example
458 of this kind of configuration file is contained in the \fB\s-1EXAMPLES\s0\fR section.
460 Alternatively if the \fBprompt\fR option is absent or not set to \fBno\fR then the
461 file contains field prompting information. It consists of lines of the form:
464 \& fieldName="prompt"
465 \& fieldName_default="default field value"
470 \&\*(L"fieldName\*(R" is the field name being used, for example commonName (or \s-1CN\s0).
471 The \*(L"prompt\*(R" string is used to ask the user to enter the relevant
472 details. If the user enters nothing then the default value is used if no
473 default value is present then the field is omitted. A field can
474 still be omitted if a default value is present if the user just
475 enters the '.' character.
477 The number of characters entered must be between the fieldName_min and
478 fieldName_max limits: there may be additional restrictions based
479 on the field being used (for example countryName can only ever be
480 two characters long and must fit in a PrintableString).
482 Some fields (such as organizationName) can be used more than once
483 in a \s-1DN\s0. This presents a problem because configuration files will
484 not recognize the same name occurring twice. To avoid this problem
485 if the fieldName contains some characters followed by a full stop
486 they will be ignored. So for example a second organizationName can
487 be input by calling it \*(L"1.organizationName\*(R".
489 The actual permitted field names are any object identifier short or
490 long names. These are compiled into OpenSSL and include the usual
491 values such as commonName, countryName, localityName, organizationName,
492 organizationUnitName, stateOrProvinceName. Additionally emailAddress
493 is include as well as name, surname, givenName initials and dnQualifier.
495 Additional object identifiers can be defined with the \fBoid_file\fR or
496 \&\fBoid_section\fR options in the configuration file. Any additional fields
497 will be treated as though they were a DirectoryString.
499 .IX Header "EXAMPLES"
500 Examine and verify certificate request:
503 \& openssl req -in req.pem -text -verify -noout
506 Create a private key and then generate a certificate request from it:
509 \& openssl genrsa -out key.pem 1024
510 \& openssl req -new -key key.pem -out req.pem
513 The same but just using req:
516 \& openssl req -newkey rsa:1024 -keyout key.pem -out req.pem
519 Generate a self signed root certificate:
522 \& openssl req -x509 -newkey rsa:1024 -keyout key.pem -out req.pem
525 Example of a file pointed to by the \fBoid_file\fR option:
528 \& 1.2.3.4 shortName A longer Name
529 \& 1.2.3.6 otherName Other longer Name
532 Example of a section pointed to by \fBoid_section\fR making use of variable
537 \& testoid2=${testoid1}.6
540 Sample configuration file prompting for field values:
544 \& default_bits = 1024
545 \& default_keyfile = privkey.pem
546 \& distinguished_name = req_distinguished_name
547 \& attributes = req_attributes
548 \& x509_extensions = v3_ca
552 \& dirstring_type = nobmp
556 \& [ req_distinguished_name ]
557 \& countryName = Country Name (2 letter code)
558 \& countryName_default = AU
559 \& countryName_min = 2
560 \& countryName_max = 2
564 \& localityName = Locality Name (eg, city)
568 \& organizationalUnitName = Organizational Unit Name (eg, section)
572 \& commonName = Common Name (eg, YOUR name)
573 \& commonName_max = 64
577 \& emailAddress = Email Address
578 \& emailAddress_max = 40
582 \& [ req_attributes ]
583 \& challengePassword = A challenge password
584 \& challengePassword_min = 4
585 \& challengePassword_max = 20
593 \& subjectKeyIdentifier=hash
594 \& authorityKeyIdentifier=keyid:always,issuer:always
595 \& basicConstraints = CA:true
598 Sample configuration containing all field values:
601 \& RANDFILE = $ENV::HOME/.rnd
606 \& default_bits = 1024
607 \& default_keyfile = keyfile.pem
608 \& distinguished_name = req_distinguished_name
609 \& attributes = req_attributes
611 \& output_password = mypass
615 \& [ req_distinguished_name ]
617 \& ST = Test State or Province
619 \& O = Organization Name
620 \& OU = Organizational Unit Name
622 \& emailAddress = test@email.address
626 \& [ req_attributes ]
627 \& challengePassword = A challenge password
631 The header and footer lines in the \fB\s-1PEM\s0\fR format are normally:
634 \& -----BEGIN CERTIFICATE REQUEST-----
635 \& -----END CERTIFICATE REQUEST-----
638 some software (some versions of Netscape certificate server) instead needs:
641 \& -----BEGIN NEW CERTIFICATE REQUEST-----
642 \& -----END NEW CERTIFICATE REQUEST-----
645 which is produced with the \fB\-newhdr\fR option but is otherwise compatible.
646 Either form is accepted transparently on input.
648 The certificate requests generated by \fBXenroll\fR with \s-1MSIE\s0 have extensions
649 added. It includes the \fBkeyUsage\fR extension which determines the type of
650 key (signature only or general purpose) and any additional OIDs entered
651 by the script in an extendedKeyUsage extension.
653 .IX Header "DIAGNOSTICS"
654 The following messages are frequently asked about:
657 \& Using configuration from /some/path/openssl.cnf
658 \& Unable to load config info
661 This is followed some time later by...
664 \& unable to find 'distinguished_name' in config
665 \& problems making Certificate Request
668 The first error message is the clue: it can't find the configuration
669 file! Certain operations (like examining a certificate request) don't
670 need a configuration file so its use isn't enforced. Generation of
671 certificates or requests however does need a configuration file. This
672 could be regarded as a bug.
674 Another puzzling message is this:
681 this is displayed when no attributes are present and the request includes
682 the correct empty \fB\s-1SET\s0 \s-1OF\s0\fR structure (the \s-1DER\s0 encoding of which is 0xa0
683 0x00). If you just see:
689 then the \fB\s-1SET\s0 \s-1OF\s0\fR is missing and the encoding is technically invalid (but
690 it is tolerated). See the description of the command line option \fB\-asn1\-kludge\fR
691 for more information.
692 .SH "ENVIRONMENT VARIABLES"
693 .IX Header "ENVIRONMENT VARIABLES"
694 The variable \fB\s-1OPENSSL_CONF\s0\fR if defined allows an alternative configuration
695 file location to be specified, it will be overridden by the \fB\-config\fR command
696 line switch if it is present. For compatibility reasons the \fB\s-1SSLEAY_CONF\s0\fR
697 environment variable serves the same purpose but its use is discouraged.
700 OpenSSL's handling of T61Strings (aka TeletexStrings) is broken: it effectively
701 treats them as \s-1ISO\-8859\-1\s0 (Latin 1), Netscape and \s-1MSIE\s0 have similar behaviour.
702 This can cause problems if you need characters that aren't available in
703 PrintableStrings and you don't want to or can't use BMPStrings.
705 As a consequence of the T61String handling the only correct way to represent
706 accented characters in OpenSSL is to use a BMPString: unfortunately Netscape
707 currently chokes on these. If you have to use accented characters with Netscape
708 and \s-1MSIE\s0 then you currently need to use the invalid T61String form.
710 The current prompting is not very friendly. It doesn't allow you to confirm what
711 you've just entered. Other things like extensions in certificate requests are
712 statically defined in the configuration file. Some of these: like an email
713 address in subjectAltName should be input by the user.
715 .IX Header "SEE ALSO"
716 \&\fIx509\fR\|(1), \fIca\fR\|(1), \fIgenrsa\fR\|(1),
717 \&\fIgendsa\fR\|(1), \fIconfig\fR\|(5)