Latest update.
This commit is contained in:
+38
-2
@@ -50,6 +50,9 @@ 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.
|
||||
|
||||
Pragmas can be specified with the B<.pragma> directive.
|
||||
See L</PRAGMAS> for mor information.
|
||||
|
||||
Each section in a configuration file consists of a number of name and
|
||||
value pairs of the form B<name=value>
|
||||
|
||||
@@ -78,6 +81,40 @@ the sequences B<\n>, B<\r>, B<\b> and B<\t> are recognized.
|
||||
All expansion and escape rules as described above that apply to B<value>
|
||||
also apply to the path of the B<.include> directive.
|
||||
|
||||
=head1 PRAGMAS
|
||||
|
||||
Pragmas can be used to change the behavior of the configuration file
|
||||
parser, among others. Currently supported pragmas are:
|
||||
|
||||
=over 4
|
||||
|
||||
=item B<.pragma> B<dollarid>:I<value>
|
||||
|
||||
I<value> can be one of:
|
||||
|
||||
=over 4
|
||||
|
||||
=item B<"on"> or B<"true">
|
||||
|
||||
this signifies that dollar signs are considered an identity character
|
||||
from this point on and that variable expansion requires the use of
|
||||
braces or parentheses. In other words, C<foo$bar> will be considered
|
||||
a name instead of C<foo> followed by the expansion of the variable
|
||||
C<bar>.
|
||||
This is suitable for platforms where the dollar sign is commonly used
|
||||
as part of names.
|
||||
|
||||
=item B<"off"> or B<"false">
|
||||
|
||||
Turns this pragma off, i.e. C<foo$bar> will be interpreted as C<foo>
|
||||
followed by the expansion of the variable C<bar>.
|
||||
|
||||
=back
|
||||
|
||||
By default, this pragma is turned off.
|
||||
|
||||
=back
|
||||
|
||||
=head1 OPENSSL LIBRARY CONFIGURATION
|
||||
|
||||
Applications can automatically configure certain
|
||||
@@ -379,7 +416,6 @@ mentioned above.
|
||||
# This is the default section.
|
||||
|
||||
HOME=/temp
|
||||
RANDFILE= ${ENV::HOME}/.rnd
|
||||
configdir=$ENV::HOME/config
|
||||
|
||||
[ section_one ]
|
||||
@@ -520,7 +556,7 @@ configuration files using that syntax will have to be modified.
|
||||
|
||||
=head1 SEE ALSO
|
||||
|
||||
L<x509(1)>, L<req(1)>, L<ca(1)>, L<fips_config(5)>
|
||||
L<openssl-x509(1)>, L<openssl-req(1)>, L<openssl-ca(1)>, L<fips_config(5)>
|
||||
|
||||
=head1 COPYRIGHT
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
=head1 NAME
|
||||
|
||||
OPENSSL FIPS CONFIGURATION
|
||||
fips_config - OpenSSL FIPS configuration
|
||||
|
||||
=head1 DESCRIPTION
|
||||
|
||||
|
||||
@@ -50,7 +50,7 @@ use is defined by the extension code itself: check out the certificate
|
||||
policies extension for an example.
|
||||
|
||||
If an extension type is unsupported then the I<arbitrary> extension syntax
|
||||
must be used, see the L<ARBITRARY EXTENSIONS|/"ARBITRARY EXTENSIONS"> section for more details.
|
||||
must be used, see the L</ARBITRARY EXTENSIONS> section for more details.
|
||||
|
||||
=head1 STANDARD EXTENSIONS
|
||||
|
||||
@@ -529,7 +529,7 @@ will only recognize the last value. This can be worked around by using the form:
|
||||
|
||||
=head1 SEE ALSO
|
||||
|
||||
L<req(1)>, L<ca(1)>, L<x509(1)>,
|
||||
L<openssl-req(1)>, L<openssl-ca(1)>, L<openssl-x509(1)>,
|
||||
L<ASN1_generate_nconf(3)>
|
||||
|
||||
=head1 COPYRIGHT
|
||||
|
||||
Reference in New Issue
Block a user