Netscape Certificate Management System 6.1, Руководство администратора

Страница: 261 / 840

Configuration Files
Chapter 7 Administrative Basics 261
Guidelines for Editing the Configuration File
The following are guidelines for editing the configuration file:
• The format for parameters is as follows:
#comment
[parameter]=value
• Comment lines begin with the pound
(#)
character and are ignored.
• A line beginning with white space is considered a continuation of the previous
line.
• Comment lines, blank lines, unknown parameters, or misspelled parameters
are ignored by the server.
• Subsystem-specific parameters are distinguished by a prefix identifying the
subsystem as follows:
❍
ca
for the Certificate Manager
❍
ra
for the Registration Manager
❍
kra
for the Data Recovery Manager
❍
ocsp
for the Online Certificate Status Manager
• The parameter names and their values are strings. The parameter names can be
hierarchically structured with
’.’
notation with multiple levels—for example,
ca.Policy.rule.RSAKeyRule.maxSize
. The entries corresponding to a lower
level (such as
Policy
in the example) can be requested from the configuration
corresponding to its higher level (
ca
in the example).
• The values that need to be localized (such as distinguished names in multibyte
format) should be entered in
utf8
format.
• The values of some parameters are referenced to other parts of the
configuration file. For example, assume that a parameter is defined as
subsystem.id=ca
; when this parameter is processed by the server, all the
parameters beginning with
ca
will be used.
• The configuration file supports Unix-style file separator, the forward slash (/).
If the backward slash (\) file separator is required, use two backward slashes
(\\) instead of one.
• Authentication parameters: