1 .\" Automatically generated by Pod::Man 2.23 (Pod::Simple 3.14)
4 .\" ========================================================================
5 .de Sp \" Vertical space (when we can't use .PP)
9 .de Vb \" Begin verbatim text
14 .de Ve \" End verbatim text
18 .\" Set up some character translations and predefined strings. \*(-- will
19 .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
20 .\" double quote, and \*(R" will give a right double quote. \*(C+ will
21 .\" give a nicer C++. Capital omega is used to do unbreakable dashes and
22 .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
23 .\" nothing in troff, for use with C<>.
25 .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
29 . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
30 . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
43 .\" Escape single quotes in literal strings from groff's Unicode transform.
47 .\" If the F register is turned on, we'll generate index entries on stderr for
48 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
49 .\" entries marked with X<> in POD. Of course, you'll have to process the
50 .\" output yourself in some meaningful fashion.
53 . tm Index:\\$1\t\\n%\t"\\$2"
63 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
64 .\" Fear. Run. Save yourself. No user-serviceable parts.
65 . \" fudge factors for nroff and troff
74 . ds #H ((1u-(\\\\n(.fu%2u))*.13m)
80 . \" simple accents for nroff and troff
90 . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
91 . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
92 . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
93 . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
94 . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
95 . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
97 . \" troff and (daisy-wheel) nroff accents
98 .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
99 .ds 8 \h'\*(#H'\(*b\h'-\*(#H'
100 .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
101 .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
102 .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
103 .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
104 .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
105 .ds ae a\h'-(\w'a'u*4/10)'e
106 .ds Ae A\h'-(\w'A'u*4/10)'E
107 . \" corrections for vroff
108 .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
109 .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
110 . \" for low resolution devices (crt and lpr)
111 .if \n(.H>23 .if \n(.V>19 \
124 .\" ========================================================================
127 .TH CONFIG 5 "2011-02-08" "1.0.0d" "OpenSSL"
128 .\" For nroff, turn off justification. Always turn off hyphenation; it makes
129 .\" way too many mistakes in technical documents.
133 config \- OpenSSL CONF library configuration files
135 .IX Header "DESCRIPTION"
136 The OpenSSL \s-1CONF\s0 library can be used to read configuration files.
137 It is used for the OpenSSL master configuration file \fBopenssl.cnf\fR
138 and in a few other places like \fB\s-1SPKAC\s0\fR files and certificate extension
139 files for the \fBx509\fR utility. OpenSSL applications can also use the
140 \&\s-1CONF\s0 library for their own purposes.
142 A configuration file is divided into a number of sections. Each section
143 starts with a line \fB[ section_name ]\fR and ends when a new section is
144 started or end of file is reached. A section name can consist of
145 alphanumeric characters and underscores.
147 The first section of a configuration file is special and is referred
148 to as the \fBdefault\fR section this is usually unnamed and is from the
149 start of file until the first named section. When a name is being looked up
150 it is first looked up in a named section (if any) and then the
153 The environment is mapped onto a section called \fB\s-1ENV\s0\fR.
155 Comments can be included by preceding them with the \fB#\fR character
157 Each section in a configuration file consists of a number of name and
158 value pairs of the form \fBname=value\fR
160 The \fBname\fR string can contain any alphanumeric characters as well as
161 a few punctuation symbols such as \fB.\fR \fB,\fR \fB;\fR and \fB_\fR.
163 The \fBvalue\fR string consists of the string following the \fB=\fR character
164 until end of line with any leading and trailing white space removed.
166 The value string undergoes variable expansion. This can be done by
167 including the form \fB\f(CB$var\fB\fR or \fB${var}\fR: this will substitute the value
168 of the named variable in the current section. It is also possible to
169 substitute a value from another section using the syntax \fB\f(CB$section::name\fB\fR
170 or \fB${section::name}\fR. By using the form \fB\f(CB$ENV::name\fB\fR environment
171 variables can be substituted. It is also possible to assign values to
172 environment variables by using the name \fBENV::name\fR, this will work
173 if the program looks up environment variables using the \fB\s-1CONF\s0\fR library
174 instead of calling \fB\f(BIgetenv()\fB\fR directly.
176 It is possible to escape certain characters by using any kind of quote
177 or the \fB\e\fR character. By making the last character of a line a \fB\e\fR
178 a \fBvalue\fR string can be spread across multiple lines. In addition
179 the sequences \fB\en\fR, \fB\er\fR, \fB\eb\fR and \fB\et\fR are recognized.
180 .SH "OPENSSL LIBRARY CONFIGURATION"
181 .IX Header "OPENSSL LIBRARY CONFIGURATION"
182 In OpenSSL 0.9.7 and later applications can automatically configure certain
183 aspects of OpenSSL using the master OpenSSL configuration file, or optionally
184 an alternative configuration file. The \fBopenssl\fR utility includes this
185 functionality: any sub command uses the master OpenSSL configuration file
186 unless an option is used in the sub command to use an alternative configuration
189 To enable library configuration the default section needs to contain an
190 appropriate line which points to the main configuration section. The default
191 name is \fBopenssl_conf\fR which is used by the \fBopenssl\fR utility. Other
192 applications may use an alternative name such as \fBmyapplicaton_conf\fR.
194 The configuration section should consist of a set of name value pairs which
195 contain specific module configuration information. The \fBname\fR represents
196 the name of the \fIconfiguration module\fR the meaning of the \fBvalue\fR is
197 module specific: it may, for example, represent a further configuration
198 section containing configuration module specific information. E.g.
201 \& openssl_conf = openssl_init
205 \& oid_section = new_oids
206 \& engines = engine_section
210 \& ... new oids here ...
214 \& ... engine stuff here ...
217 Currently there are two configuration modules. One for \s-1ASN1\s0 objects another
218 for \s-1ENGINE\s0 configuration.
219 .SS "\s-1ASN1\s0 \s-1OBJECT\s0 \s-1CONFIGURATION\s0 \s-1MODULE\s0"
220 .IX Subsection "ASN1 OBJECT CONFIGURATION MODULE"
221 This module has the name \fBoid_section\fR. The value of this variable points
222 to a section containing name value pairs of OIDs: the name is the \s-1OID\s0 short
223 and long name, the value is the numerical form of the \s-1OID\s0. Although some of
224 the \fBopenssl\fR utility sub commands already have their own \s-1ASN1\s0 \s-1OBJECT\s0 section
225 functionality not all do. By using the \s-1ASN1\s0 \s-1OBJECT\s0 configuration module
226 \&\fBall\fR the \fBopenssl\fR utility sub commands can see the new objects as well
227 as any compliant applications. For example:
232 \& some_new_oid = 1.2.3.4
233 \& some_other_oid = 1.2.3.5
236 In OpenSSL 0.9.8 it is also possible to set the value to the long name followed
237 by a comma and the numerical \s-1OID\s0 form. For example:
240 \& shortName = some object long name, 1.2.3.4
242 .SS "\s-1ENGINE\s0 \s-1CONFIGURATION\s0 \s-1MODULE\s0"
243 .IX Subsection "ENGINE CONFIGURATION MODULE"
244 This \s-1ENGINE\s0 configuration module has the name \fBengines\fR. The value of this
245 variable points to a section containing further \s-1ENGINE\s0 configuration
248 The section pointed to by \fBengines\fR is a table of engine names (though see
249 \&\fBengine_id\fR below) and further sections containing configuration informations
250 specific to each \s-1ENGINE\s0.
252 Each \s-1ENGINE\s0 specific section is used to set default algorithms, load
253 dynamic, perform initialization and send ctrls. The actual operation performed
254 depends on the \fIcommand\fR name which is the name of the name value pair. The
255 currently supported commands are listed below.
262 \& # Configure ENGINE named "foo"
264 \& # Configure ENGINE named "bar"
268 \& ... foo ENGINE specific commands ...
271 \& ... "bar" ENGINE specific commands ...
274 The command \fBengine_id\fR is used to give the \s-1ENGINE\s0 name. If used this
275 command must be first. For example:
279 \& # This would normally handle an ENGINE named "foo"
283 \& # Override default name and use "myfoo" instead.
287 The command \fBdynamic_path\fR loads and adds an \s-1ENGINE\s0 from the given path. It
288 is equivalent to sending the ctrls \fB\s-1SO_PATH\s0\fR with the path argument followed
289 by \fB\s-1LIST_ADD\s0\fR with value 2 and \fB\s-1LOAD\s0\fR to the dynamic \s-1ENGINE\s0. If this is
290 not the required behaviour then alternative ctrls can be sent directly
291 to the dynamic \s-1ENGINE\s0 using ctrl commands.
293 The command \fBinit\fR determines whether to initialize the \s-1ENGINE\s0. If the value
294 is \fB0\fR the \s-1ENGINE\s0 will not be initialized, if \fB1\fR and attempt it made to
295 initialized the \s-1ENGINE\s0 immediately. If the \fBinit\fR command is not present
296 then an attempt will be made to initialize the \s-1ENGINE\s0 after all commands in
297 its section have been processed.
299 The command \fBdefault_algorithms\fR sets the default algorithms an \s-1ENGINE\s0 will
300 supply using the functions \fB\f(BIENGINE_set_default_string()\fB\fR
302 If the name matches none of the above command names it is assumed to be a
303 ctrl command which is sent to the \s-1ENGINE\s0. The value of the command is the
304 argument to the ctrl command. If the value is the string \fB\s-1EMPTY\s0\fR then no
305 value is sent to the command.
312 \& # Configure ENGINE named "foo"
316 \& # Load engine from DSO
317 \& dynamic_path = /some/path/fooengine.so
318 \& # A foo specific ctrl.
319 \& some_ctrl = some_value
320 \& # Another ctrl that doesn\*(Aqt take a value.
321 \& other_ctrl = EMPTY
322 \& # Supply all default algorithms
323 \& default_algorithms = ALL
327 If a configuration file attempts to expand a variable that doesn't exist
328 then an error is flagged and the file will not load. This can happen
329 if an attempt is made to expand an environment variable that doesn't
330 exist. For example in a previous version of OpenSSL the default OpenSSL
331 master configuration file used the value of \fB\s-1HOME\s0\fR which may not be
332 defined on non Unix systems and would cause an error.
334 This can be worked around by including a \fBdefault\fR section to provide
335 a default value: then if the environment lookup fails the default value
336 will be used instead. For this to work properly the default value must
337 be defined earlier in the configuration file than the expansion. See
338 the \fB\s-1EXAMPLES\s0\fR section for an example of how to do this.
340 If the same variable exists in the same section then all but the last
341 value will be silently ignored. In certain circumstances such as with
342 DNs the same field may occur multiple times. This is usually worked
343 around by ignoring any characters before an initial \fB.\fR e.g.
346 \& 1.OU="My first OU"
347 \& 2.OU="My Second OU"
350 .IX Header "EXAMPLES"
351 Here is a sample configuration file using some of the features
355 \& # This is the default section.
358 \& RANDFILE= ${ENV::HOME}/.rnd
359 \& configdir=$ENV::HOME/config
363 \& # We are now in section one.
365 \& # Quotes permit leading and trailing whitespace
366 \& any = " any variable name "
368 \& other = A string that can \e
369 \& cover several lines \e
370 \& by including \e\e characters
372 \& message = Hello World\en
376 \& greeting = $section_one::message
379 This next example shows how to expand environment variables safely.
381 Suppose you want a variable called \fBtmpfile\fR to refer to a
382 temporary filename. The directory it is placed in can determined by
383 the the \fB\s-1TEMP\s0\fR or \fB\s-1TMP\s0\fR environment variables but they may not be
384 set to any value at all. If you just include the environment variable
385 names and the variable doesn't exist then this will cause an error when
386 an attempt is made to load the configuration file. By making use of the
387 default section both values can be looked up with \fB\s-1TEMP\s0\fR taking
388 priority and \fB/tmp\fR used if neither is defined:
392 \& # The above value is used if TMP isn\*(Aqt in the environment
394 \& # The above value is used if TEMP isn\*(Aqt in the environment
395 \& tmpfile=${ENV::TEMP}/tmp.filename
399 Currently there is no way to include characters using the octal \fB\ennn\fR
400 form. Strings are all null terminated so nulls cannot form part of
403 The escaping isn't quite right: if you want to use sequences like \fB\en\fR
404 you can't use any quote escaping on the same line.
406 Files are loaded in a single pass. This means that an variable expansion
407 will only work if the variables referenced are defined earlier in the
410 .IX Header "SEE ALSO"
411 \&\fIx509\fR\|(1), \fIreq\fR\|(1), \fIca\fR\|(1)
projects / dragonfly.git / blob