 以 PDF 格式下載這本書 (3630 KB)
File Formatscertmap.conf(4)NAME | Synopsis | Description | Examples | Attributes | See Also NAME
SynopsisLocation: instance-path/alias/certmap.conf # This is a comment. certmap default default [default:property1 [value1]] [default:property2 [value2]] […] [certmap name issuerDN [name:property1 [value1]] [name:property2 [value2]] … ] DescriptionThe certmap.conf file defines how Directory Server maps certificates to directory entries. Comment lines are those starting with #. CERTIFICATE MAPPINGScertmap default default Each subsequent certificate map starts with a line identifying the name of the map and the certificate authority issuer DN of the certificates to which the map applies. The issuerDN string specified in the certificate map must correspond exactly to the issuer DN shown in the certificates. In particular, whitespace in the issuer DN is significant. PROPERTIES AND VALUES
A certificate map also optionally specifies values for the following properties. ExamplesThe following certmap.conf file specifies both a default certificate map, and an additional certificate map for certificates from the US subsidiary of Example.com. # Example certmap.conf certmap default default certmap examplecerts ou=Example.com, o=examplecerts, c=US examplecerts:DNComps ou,o,c examplecerts:FilterComps e examplecerts:verifycert on When the server gets a certificate issued by any certificate authority other than the US subsidiary of Example.com, it uses the default mapping. If the certificate however has been issued by the US subsidiary of Example.com, the server looks for entries under the branch for the organizational unit and searches for entries using the client email address. It also verifies that such certificates are valid and that they are not revoked. AttributesSee attributes(5) for descriptions of the following attributes:
See AlsoDS 6.2 Last Revised May 19, 2006NAME | Synopsis | Description | Examples | Attributes | See Also dse.ldif(4)NAME | Synopsis | Description | Extended Description | CONFIGURATION ATTRIBUTES | Attributes | Attributes NAME
SynopsisLocation: instance-path/config/dse.ldif Location: instance-path/conf_bk/dse.ldif Description
Directory Server stores its configuration as directory entries under cn=config. You can therefore change the server configuration by modifying configuration entries over LDAP, rather than by editing configuration files. Configuring Directory Server in this way allows you to reconfigure a remote server while it continues to serve other directory clients. The dse.ldif file defines the configuration for a Directory Server instance. The dse.ldif file includes a set of entries under cn=config. These entries make up the modular parts of the Directory Server instance configuration. Directory Server stores its schema under cn=schema, not as part of the rest of the server configuration. For an introduction to the schema available under cn=schema, see Intro(5DSSD). Note – Neither the dse.ldif file nor the cn=config suffix constitute a public interface for configuring a Directory Server instance. Use dsconf(1M) instead. The dse.ldif file has the following characteristics. Extended Description
Directory Server has a modular configuration, with a number of distinct branches under the cn=config Directory Information Tree. The primary branches are below the following DNs. About Configuration AttributesThe dse.ldif file contains all configuration information including directory specific entries created by Directory Server at startup, and directory specific entries related to the database, also created by Directory Server at startup. The file includes the Root DSE, named by "", and the entire contents of cn=config. When the server generates the dse.ldif file, it lists the entries in hierarchical order. It does so in the order that the entries appear in the directory under cn=config. Within a configuration entry, each attribute is represented as an attribute name. The value of the attribute corresponds to the attribute’s configuration. The following example shows part of the dse.ldif file for a Directory Server instance. The example indicates, among other things, that schema checking has been turned on. This is represented by the attribute nsslapd-schemacheck, which takes the value on. dn: cn=config objectclass: top objectclass: extensibleObject objectclass: nsslapdConfig nsslapd-accesslog-logging-enabled: on nsslapd-enquote-sup-oc: on nsslapd-localhost: myServer.example.com nsslapd-errorlog: /local/ds/logs/errors nsslapd-schemacheck: on nsslapd-port: 389 nsslapd-localuser: nobody … See CONFIGURATION ATTRIBUTES in this manual page for a list of configuration attribute manual pages. Access Control For Configuration EntriesWhen Directory Server is installed, a default set of Access Control Instructions, ACIs, is implemented for all entries under cn=config. The following extract from the dse.ldif file shows an example of these default ACIs. aci: (targetattr != "aci") (targetscope = "base") (version 3.0; aci "Enable read access to rootdse for anonymous users"; allow(read,search,compare) userdn="ldap:///anyone"; ) aci: (targetattr = "*") (version 3.0; acl "Enable full access for Administrators group"; allow (all)(groupdn = " ldap:///cn=Administrators,cn=config"); ) aci: (targetattr = "userPassword") ( version 3.0; acl "allow userpassword self modification"; allow (write) userdn = "ldap:///self";) By default, both the cn=Directory Manager user and the cn=admin,cn=Administrators,cn=config user have access to modify configuration entries. ACI syntax is covered elsewhere in the Directory Server Enterprise Edition documentation. CONFIGURATION ATTRIBUTESThis section lists configuration attributes by their location in the configuration Directory Information Tree. Attributes of cn=configGeneral configuration entries are stored under the cn=config entry. The cn=config entry is an instance of the nsslapdConfig object class, which inherits from the extensibleObject object class. For attributes to be taken into account by the server, the entry must contain the nsslapdConfig object class, the extensibleObject object class and the top object class. See the following manual pages. Attributes of cn=encryption,cn=configEncryption related attributes are stored under the cn=encryption,cn=config entry. This entry is an instance of the nsEncryptionConfig object class. For encryption related attributes to be taken into account by the server, this object class, in addition to the top object class, must be present in the entry. See the following manual pages. Attributes of cn=mapping tree,cn=configcn="suffixName",cn=mapping tree,cn=config Suffix configuration entries therefore have CNs such as cn="dc=example,dc=com". Suffix configuration entries are instances of the nsMappingTree object class, which inherits from the extensibleObject object class. For suffix configuration attributes to be taken into account by the server, these object classes, in addition to the top object class, must be present in the entry. See the following man pages about suffix configuration entry attributes. Replication configuration attributes are stored under an entry with a DN of the following form. cn=replica,cn="suffixName",cn=mapping tree,cn=config Replication agreement attributes are stored under an entry with a DN of the following form. cn=replicationAgreementName,cn=replica,cn="suffixName", cn=mapping tree,cn=config See replication(5dsconf) for details. Attributes of cn=Password PolicyThe default password policy entry for a Directory Server instance has DN cn=Password Policy,cn=config. For help configuring password policy, see the Directory Server Administration Guide. For details concerning password policy entries, see pwpolicy(5dssd). Entries having the object classes described in pwdPolicy(5dsoc), and in sunPwdPolicy(5dsoc) are used to configure password policy. For instructions concerning legacy password policy functionality, see the Directory Server Migration Guide. Legacy password policy functionality is configured using entries of the object class described in passwordPolicy(5dsoc). Plug-In Configuration Under cn=pluginsMany of the features of Directory Server are designed as discrete modules that plug into the core server. The configuration for each part of Directory Server plug-in functionality has its own separate entry and set of attributes under the subtree cn=plugins,cn=config. The following example shows the configuration entry for the Telephone Syntax plug-in. dn: cn=Telephone Syntax,cn=plugins,cn=config objectclass: top objectclass: nsSlapdPlugin objectclass: ds-signedPlugin objectclass: extensibleObject cn: Telephone Syntax nsslapd-pluginPath: /opt/SUNWdsee/ds6/lib/syntax-plugin.so nsslapd-pluginInitfunc: tel_init nsslapd-pluginType: syntax nsslapd-pluginEnabled: on … Some of these attributes are common to all plug-ins and some may be particular to a specific plug-in. Chained Suffix Plug-In Configuration
All plug-in configuration information used by the chained suffix instances is stored under the cn=chaining database,cn=plugins,cn=config entry. The following global chained suffix configuration attributes common to all instances are stored under cn=config,cn=chaining database,cn=plugins,cn=config. Default instance chained suffix attributes are stored under cn=default instance config,cn=chaining database,cn=plugins,cn=config. Instance-specific chained suffix attributes are stored under cn=chainedSuffix,cn=chaining database,cn=plugins,cn=config. The following list shows the chained suffix attributes used for monitoring activity on instances. These attributes are stored under cn=monitor,cn=dbName, cn=chaining database,cn=plugins,cn=config. Database Plug-In Configuration
Database plug-in configuration entries are stored under cn=ldbm database,cn=plugins,cn=config. That entry is a server plug-in configuration entry for databases, and therefore takes the same attributes as other plug-in entries. Key entries beneath the plug-in configuration entry are listed as follows. DSML Front End Plug-In Configuration AttributesThe front end plug-in enables you to access directory data by methods other than LDAP. Directory Server provides a DSML front end plug-in that enables access using DSMLv2 over HTTP/SOAP. Attributes for the DSML front end plug-in are stored under cn=DSMLv2-SOAP-HTTP,cn=frontends,cn=plugins,cn=config. See the following manual pages for details. Retro Changelog Plug-In ConfigurationServer Plug-In Configuration EntriesAll plug-ins are instances of the nsSlapdPlugin object class, which in turn inherits from the extensibleObject object class. For plug-in configuration attributes to be taken into account by the server, both of these object classes, in addition to the top object class, must be present in the entry. See nsslapd-plugin(5dsconf) for an overview of the plug-ins provided with Directory Server, including configurable options, configurable arguments, default setting, dependencies, general performance related information, and further reading. Attributes of cn=uniqueid generator,cn=configUnique ID generator configuration attributes are stored under the entry with DN cn=uniqueid generator,cn=config. The cn=uniqueid generator,cn=config entry is an instance of the extensibleObject object class. For unique ID generator configuration attributes to be taken into account by the server, this object class, in addition to the top object class, must be present in the entry. The principal unique ID generator attribute is nsState(5dsconf). Attributes
This section lists configuration elements whose modifications cannot take effect dynamically, while the server is still running. After modifying these parameters, you must restart the server. The following list shoiws the configuration attributes concerned, with their full DNs, and provides a brief description of their functions. AttributesSee attributes(5) for descriptions of the following attributes:
NAME | Synopsis | Description | Extended Description | CONFIGURATION ATTRIBUTES | Attributes | Attributes hosts_access(4)NAME | Synopsis | Description | Examples | Diagnostics | Files | See Also | Bugs | AUTHOR | Attributes NAME
Synopsisinstance-path/config/hosts.allow instance-path/config/hosts.deny Description
This manual page describes a simple access control language that is based on client (host name/address, user name), and server (process name, host name/address) patterns. Examples are given at the end. The impatient reader is encouraged to skip to the EXAMPLES section for a quick introduction. In the following text, daemon is the the process name of a network daemon process, and client is the name and/or address of a host requesting service. Note that the version of hosts_access supplied with Directory Server Enterprise Edition is different from the version delivered with Solaris. The Directory Server Enterprise Edition version of hosts_access has the following characteristics: ACCESS CONTROL FILESThe access control software consults two files. The search stops at the first match: A non-existing access control file is treated as if it were an empty file. Thus, access control can be turned off by providing no access control files. ACCESS CONTROL RULESEach access control file consists of zero or more lines of text. These lines are processed in order of appearance. The search terminates when a match is found. PATTERNSThe access control language implements the following patterns: WILDCARDSWildcards `*' and `?' can be used to match hostnames or IP addresses. However, this method of matching cannot be used in conjunction with the following: net/mask matching, hostname matching beginning with `.' , IP address matching ending with `.' or a IPv6 rule (begins with '['). The access control language supports explicit wildcards: OPERATORSSHELL COMMANDSNote that shell commands are not available on Microsoft Windows. % EXPANSIONSThe following expansions are available within shell commands: Characters in % expansions that may confuse the shell are replaced by underscores. ExamplesThe language is flexible enough that different types of access control policy can be expressed with a minimum of fuss. Although the language uses two access control tables, the most common policies can be implemented with one of the tables being trivial or even empty. When reading the examples below it is important to realize that the allow table is scanned before the deny table, that the search terminates when a match is found, and that access is granted when no match is found at all. The examples use host and domain names. They can be improved by including address and/or network/netmask information, to reduce the impact of temporary name server lookup failures. MOSTLY CLOSEDIn this case, access is denied by default. Only explicitly authorized hosts are permitted access. The default policy (no access) is implemented with a trivial deny file:
This denies all service to all hosts, unless they are permitted access by entries in the allow file. The explicitly authorized hosts are listed in the allow file. For example:
The first rule permits access from hosts in the local domain (no `.' in the host name). The second rule permits access from all hosts in the .foobar.edu domain (notice the leading period), with the exception of terminalserver.foobar.edu. MOSTLY OPENHere, access is granted by default; only explicitly specified hosts are refused service. The default policy (access granted) makes the allow file redundant so that it can be omitted. The explicitly non-authorized hosts are listed in the deny file. For example:
The first rule denies some hosts and domains all services; the second rule still permits connections to directory port 1389 from other hosts and domains. BOOBY TRAPSThe next example permits requests to Directory Server port 1389 from hosts in the local domain (notice the leading dot). Requests from any other hosts are denied. Instead of the requested file, a finger probe is sent to the offending host. The result is mailed to the superuser.
The above example assumes that the safe_finger command is installed in /usr/sfw/sbin. For Solaris, the safe_finger command is in the SUNWtcpd package. The default location for the safe_finger command in the SUNWtcpd package is "/usr/sfw/sbin". For other operating systems the safe_finger command should be installed in a suitable place. The safe_finger command limits possible damage from data sent by the remote finger server, and gives better protection than the standard finger command. Shell commands for Windows is not supported, so Windows users should not use this rule. The expansion of the %h (client host) and %d (service name) sequences is described in the section on shell commands. Warning: do not booby-trap your finger daemon, unless you are prepared for infinite finger loops. On network firewall systems this trick can be carried even further. The typical network firewall only provides a limited set of services to the outer world. All other services can be "bugged" just like the above tftp example. The result is an excellent early-warning system. DiagnosticsAn error is reported when a syntax error is found in a host access control rule; when the length of an access control rule exceeds the capacity of an internal buffer (2048); when an access control rule is not terminated by a newline character; when the result of %letter expansion would overflow an internal buffer; when a system call fails that should not. All problems are written to the Directory Server instance access log. Filesinstance-path/config/hosts.allow, (daemon,client) pairs are granted access. instance-path/config/hosts.deny, (daemon,client) pairs are denied access. See Alsotcpd(1M) tcp/ip daemon wrapper program. tcpdchk(1M), tcpdmatch(1M), test programs. BugsIf a name server lookup times out, the host name will not be available to the access control software, even though the host is registered. AUTHORWietse Venema (wietse@wzv.win.tue.nl) Department of Mathematics and Computing Science Eindhoven University of Technology Den Dolech 2, P.O. Box 513, 5600 MB Eindhoven, The Netherlands AttributesSee attributes(5) for descriptions of the following attributes:
NAME | Synopsis | Description | Examples | Diagnostics | Files | See Also | Bugs | AUTHOR | Attributes |
||||||||||||||||||||||||
|