A configuration file is divided into a number of sections. Each section starts with a line [[ sseeccttiioonn__nnaammee ]] and ends when a new section is started or end of file is reached. A section name can consist of alphanumeric characters and underscores.
The first section of a configuration file is special and is referred to as the ddeeffaauulltt section this is usually unnamed and is from the start of file until the first named section. When a name is being looked up it is first looked up in a named section (if any) and then the default section.
The environment is mapped onto a section called EENNVV.
Comments can be included by preceding them with the ## character
Each section in a configuration file consists of a number of name and value pairs of the form nnaammee==vvaalluuee
The nnaammee string can contain any alphanumeric characters as well as a few punctuation symbols such as .. ,, ;; and __.
The vvaalluuee string consists of the string following the == character until end of line with any leading and trailing white space removed.
The value string undergoes variable expansion. This can be done by including the form $$vvaarr or $${{vvaarr}}: this will substitute the value of the named variable in the current section. It is also possible to substitute a value from another section using the syntax $$sseeccttiioonn::::nnaammee or $${{sseeccttiioonn::::nnaammee}}. By using the form $$EENNVV::::nnaammee environment variables can be substituted. It is also possible to assign values to environment variables by using the name EENNVV::::nnaammee, this will work if the program looks up environment variables using the CCOONNFF library instead of calling _gg_ee_tt_ee_nn_vv_((_)) directly.
It is possible to escape certain characters by using any kind of quote or the \\ character. By making the last character of a line a \\ a vvaalluuee string can be spread across multiple lines. In addition the sequences \\nn, \\rr, \\bb and \\tt are recognized.
To enable library configuration the default section needs to contain an appropriate line which points to the main configuration section. The default name is ooppeennssssll__ccoonnff which is used by the ooppeennssssll utility. Other applications may use an alternative name such as mmyyaapppplliiccaattoonn__ccoonnff.
The configuration section should consist of a set of name value pairs which contain specific module configuration information. The nnaammee represents the name of the _c_o_n_f_i_g_u_r_a_t_i_o_n _m_o_d_u_l_e the meaning of the vvaalluuee is module specific: it may, for example, represent a further configuration section containing configuration module specific information. E.g.
openssl_conf = openssl_init
[openssl_init]
oid_section = new_oids engines = engine_section
[new_oids]
... new oids here ...
[engine_section]
... engine stuff here ...
Currently there are two configuration modules. One for ASN1 objects another
for ENGINE configuration.
AASSNN11 OOBBJJEECCTT CCOONNFFIIGGUURRAATTIIOONN MMOODDUULLEE
This module has the name ooiidd__sseeccttiioonn. The value of this variable points to a section containing name value pairs of OIDs: the name is the OID short and long name, the value is the numerical form of the OID. Although some of the ooppeennssssll utility sub commands already have their own ASN1 OBJECT section functionality not all do. By using the ASN1 OBJECT configuration module aallll the ooppeennssssll utility sub commands can see the new objects as well as any compliant applications. For example:
[new_oids]
some_new_oid = 1.2.3.4 some_other_oid = 1.2.3.5
In OpenSSL 0.9.8 it is also possible to set the value to the long name followed by a comma and the numerical OID form. For example:
shortName = some object long name, 1.2.3.4
EENNGGIINNEE CCOONNFFIIGGUURRAATTIIOONN MMOODDUULLEE
This ENGINE configuration module has the name eennggiinneess. The value of this variable points to a section containing further ENGINE configuration information.
The section pointed to by eennggiinneess is a table of engine names (though see eennggiinnee__iidd below) and further sections containing configuration informations specific to each ENGINE.
Each ENGINE specific section is used to set default algorithms, load dynamic, perform initialization and send ctrls. The actual operation performed depends on the _c_o_m_m_a_n_d name which is the name of the name value pair. The currently supported commands are listed below.
For example:
[engine_section]
# Configure ENGINE named "foo" foo = foo_section # Configure ENGINE named "bar" bar = bar_section
[foo_section] ... foo ENGINE specific commands ...
[bar_section] ... "bar" ENGINE specific commands ...
The command eennggiinnee__iidd is used to give the ENGINE name. If used this command must be first. For example:
[engine_section] # This would normally handle an ENGINE named "foo" foo = foo_section
[foo_section] # Override default name and use "myfoo" instead. engine_id = myfoo
The command ddyynnaammiicc__ppaatthh loads and adds an ENGINE from the given path. It is equivalent to sending the ctrls SSOO__PPAATTHH with the path argument followed by LLIISSTT__AADDDD with value 2 and LLOOAADD to the dynamic ENGINE. If this is not the required behaviour then alternative ctrls can be sent directly to the dynamic ENGINE using ctrl commands.
The command iinniitt determines whether to initialize the ENGINE. If the value is 00 the ENGINE will not be initialized, if 11 and attempt it made to initialized the ENGINE immediately. If the iinniitt command is not present then an attempt will be made to initialize the ENGINE after all commands in its section have been processed.
The command ddeeffaauulltt__aallggoorriitthhmmss sets the default algorithms an ENGINE will supply using the functions _EE_NN_GG_II_NN_EE____ss_ee_tt____dd_ee_ff_aa_uu_ll_tt____ss_tt_rr_ii_nn_gg_((_))
If the name matches none of the above command names it is assumed to be a ctrl command which is sent to the ENGINE. The value of the command is the argument to the ctrl command. If the value is the string EEMMPPTTYY then no value is sent to the command.
For example:
[engine_section]
# Configure ENGINE named "foo" foo = foo_section
[foo_section] # Load engine from DSO dynamic_path = /some/path/fooengine.so # A foo specific ctrl. some_ctrl = some_value # Another ctrl that doesn't take a value. other_ctrl = EMPTY # Supply all default algorithms default_algorithms = ALL
This can be worked around by including a ddeeffaauulltt section to provide a default value: then if the environment lookup fails the default value will be used instead. For this to work properly the default value must be defined earlier in the configuration file than the expansion. See the EEXXAAMMPPLLEESS section for an example of how to do this.
If the same variable exists in the same section then all but the last value will be silently ignored. In certain circumstances such as with DNs the same field may occur multiple times. This is usually worked around by ignoring any characters before an initial .. e.g.
1.OU="My first OU" 2.OU="My Second OU"
# This is the default section.
HOME=/temp RANDFILE= ${ENV::HOME}/.rnd configdir=$ENV::HOME/config
[ section_one ]
# We are now in section one.
# Quotes permit leading and trailing whitespace any = " any variable name "
other = A string that can \ cover several lines \ by including \\ characters
message = Hello World\n
[ section_two ]
greeting = $section_one::message
This next example shows how to expand environment variables safely.
Suppose you want a variable called ttmmppffiillee to refer to a temporary filename. The directory it is placed in can determined by the the TTEEMMPP or TTMMPP environment variables but they may not be set to any value at all. If you just include the environment variable names and the variable doesn't exist then this will cause an error when an attempt is made to load the configuration file. By making use of the default section both values can be looked up with TTEEMMPP taking priority and //ttmmpp used if neither is defined:
TMP=/tmp # The above value is used if TMP isn't in the environment TEMP=$ENV::TMP # The above value is used if TEMP isn't in the environment tmpfile=${ENV::TEMP}/tmp.filename
The escaping isn't quite right: if you want to use sequences like \\nn you can't use any quote escaping on the same line.
Files are loaded in a single pass. This means that an variable expansion will only work if the variables referenced are defined earlier in the file.