summaryrefslogtreecommitdiff
path: root/src/lib/libssl/src/doc/apps/config.pod
diff options
context:
space:
mode:
Diffstat (limited to 'src/lib/libssl/src/doc/apps/config.pod')
-rw-r--r--src/lib/libssl/src/doc/apps/config.pod14
1 files changed, 7 insertions, 7 deletions
diff --git a/src/lib/libssl/src/doc/apps/config.pod b/src/lib/libssl/src/doc/apps/config.pod
index 25c5381b9d..d018dfce50 100644
--- a/src/lib/libssl/src/doc/apps/config.pod
+++ b/src/lib/libssl/src/doc/apps/config.pod
@@ -63,14 +63,14 @@ functionality: any sub command uses the master OpenSSL configuration file
63unless an option is used in the sub command to use an alternative configuration 63unless an option is used in the sub command to use an alternative configuration
64file. 64file.
65 65
66To enable library configuration the default section needs to contain an 66To enable library configuration the default section needs to contain an
67appropriate line which points to the main configuration section. The default 67appropriate line which points to the main configuration section. The default
68name is B<openssl_conf> which is used by the B<openssl> utility. Other 68name is B<openssl_conf> which is used by the B<openssl> utility. Other
69applications may use an alternative name such as B<myapplicaton_conf>. 69applications may use an alternative name such as B<myapplicaton_conf>.
70 70
71The configuration section should consist of a set of name value pairs which 71The configuration section should consist of a set of name value pairs which
72contain specific module configuration information. The B<name> represents 72contain specific module configuration information. The B<name> represents
73the name of the I<configuration module> the meaning of the B<value> is 73the name of the I<configuration module> the meaning of the B<value> is
74module specific: it may, for example, represent a further configuration 74module specific: it may, for example, represent a further configuration
75section containing configuration module specific information. E.g. 75section containing configuration module specific information. E.g.
76 76
@@ -103,7 +103,7 @@ B<all> the B<openssl> utility sub commands can see the new objects as well
103as any compliant applications. For example: 103as any compliant applications. For example:
104 104
105 [new_oids] 105 [new_oids]
106 106
107 some_new_oid = 1.2.3.4 107 some_new_oid = 1.2.3.4
108 some_other_oid = 1.2.3.5 108 some_other_oid = 1.2.3.5
109 109
@@ -142,7 +142,7 @@ For example:
142 [bar_section] 142 [bar_section]
143 ... "bar" ENGINE specific commands ... 143 ... "bar" ENGINE specific commands ...
144 144
145The command B<engine_id> is used to give the ENGINE name. If used this 145The command B<engine_id> is used to give the ENGINE name. If used this
146command must be first. For example: 146command must be first. For example:
147 147
148 [engine_section] 148 [engine_section]
@@ -169,7 +169,7 @@ The command B<default_algorithms> sets the default algorithms an ENGINE will
169supply using the functions B<ENGINE_set_default_string()> 169supply using the functions B<ENGINE_set_default_string()>
170 170
171If the name matches none of the above command names it is assumed to be a 171If the name matches none of the above command names it is assumed to be a
172ctrl command which is sent to the ENGINE. The value of the command is the 172ctrl command which is sent to the ENGINE. The value of the command is the
173argument to the ctrl command. If the value is the string B<EMPTY> then no 173argument to the ctrl command. If the value is the string B<EMPTY> then no
174value is sent to the command. 174value is sent to the command.
175 175
@@ -220,7 +220,7 @@ Here is a sample configuration file using some of the features
220mentioned above. 220mentioned above.
221 221
222 # This is the default section. 222 # This is the default section.
223 223
224 HOME=/temp 224 HOME=/temp
225 RANDFILE= ${ENV::HOME}/.rnd 225 RANDFILE= ${ENV::HOME}/.rnd
226 configdir=$ENV::HOME/config 226 configdir=$ENV::HOME/config
@@ -250,7 +250,7 @@ the the B<TEMP> or B<TMP> environment variables but they may not be
250set to any value at all. If you just include the environment variable 250set to any value at all. If you just include the environment variable
251names and the variable doesn't exist then this will cause an error when 251names and the variable doesn't exist then this will cause an error when
252an attempt is made to load the configuration file. By making use of the 252an attempt is made to load the configuration file. By making use of the
253default section both values can be looked up with B<TEMP> taking 253default section both values can be looked up with B<TEMP> taking
254priority and B</tmp> used if neither is defined: 254priority and B</tmp> used if neither is defined:
255 255
256 TMP=/tmp 256 TMP=/tmp