Latest update.
This commit is contained in:
@@ -42,6 +42,13 @@ working directory so unless the configuration file containing the
|
||||
B<.include> directive is application specific the inclusion will not
|
||||
work as expected.
|
||||
|
||||
There can be optional B<=> character and whitespace characters between
|
||||
B<.include> directive and the path which can be useful in cases the
|
||||
configuration file needs to be loaded by old OpenSSL versions which do
|
||||
not support the B<.include> syntax. They would bail out with error
|
||||
if the B<=> character is not present but with it they just ignore
|
||||
the include.
|
||||
|
||||
Each section in a configuration file consists of a number of name and
|
||||
value pairs of the form B<name=value>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user