ods-enforcerd(8) [debian man page]
ods-enforcerd(8) OpenDNSSEC ods-enforcerd ods-enforcerd(8) NAME
ods-enforcerd - OpenDNSSEC Policy Enforcer daemon SYNOPSIS
ods-enforcerd [-c FILE] [-d] [-1] [-P PIDFILE] [-v] [-h] DESCRIPTION
ods-enforcerd is part of the OpenDNSSEC software. It will enforce any policies that you have set up for zones under the control of OpenDNSSEC (including the generation of keys if configured to). For more information, go to http://www.opendnssec.org and visit the Docu- mentation page. Invoked with no arguments, ods-enforcerd will read the default configuration file /etc/opendnssec/conf.xml and act according to its con- tents. OPTIONS
-c FILE Use alternate conf.xml. -d Run in debug mode. -1 Run once, then exit. -P PIDFILE Use alternate process-id file. -v Print the version, then exit. -h Show help, then exit. SIGNALS
The ods-enforcerd can be controlled using the ods-control utility. Signals may also be used. SIGHUP ods-enforcerd runs on a schedule defined in conf.xml; this signal will interrupt that and force the daemon to wake up. SIGINT, SIGTERM Force the daemon to stop (if it is running it will finish what it is doing first). CONFIGURATION
The configuration of ods-enforcerd is contained in the conf.xml file; the options available are described in the OpenDNSSEC documentation. DIAGNOSTICS
will log all the problems via the standard syslog(8) daemon facility. FILES
/etc/opendnssec/conf.xml default configuration file. /var/run/opendnssec/zone_fetcher.pid default process-id file. SEE ALSO
ods-auditor(1), ods-control(8), ods-hsmspeed(1), ods-hsmutil(1), ods-kaspcheck(1), ods-ksmutil(1), ods-signer(8), ods-signerd(8), ods-tim- ing(5), opendnssec(7), http://www.opendnssec.org/ AUTHORS
ods-enforcerd was written by John Dickinson and Nominet as part of the OpenDNSSEC project. OpenDNSSEC February 2010 ods-enforcerd(8)
Check Out this Related Man Page
rlm_pap(5) FreeRADIUS Module rlm_pap(5) NAME
rlm_pap - FreeRADIUS Module DESCRIPTION
The rlm_pap module authenticates RADIUS Access-Request packets that contain a User-Password attribute. The module should also be listed last in the authorize section, so that it can set the Auth-Type attribute as appropriate. When a RADIUS packet contains a clear-text password in the form of a User-Password attribute, the rlm_pap module may be used for authenti- cation. The module requires a "known good" password, which it uses to validate the password given in the RADIUS packet. That "known good" password must be supplied by another module (e.g. rlm_files, rlm_ldap, etc.), and is usually taken from a database. CONFIGURATION
The only relevant configuration item is: auto_header If set to "yes", the module will look inside of the User-Password attribute for the headers {crypt}, {clear}, etc., and will auto- matically create the appropriate attribute, with the correct value. This module understands many kinds of password hashing methods, as given by the following table. Header Attribute Description ------ --------- ----------- {clear} Cleartext-Password clear-text passwords {cleartext} Cleartext-Password clear-text passwords {crypt} Crypt-Password Unix-style "crypt"ed passwords {md5} MD5-Password MD5 hashed passwords {smd5} SMD5-Password MD5 hashed passwords, with a salt {sha} SHA-Password SHA1 hashed passwords {ssha} SSHA-Password SHA1 hashed passwords, with a salt {nt} NT-Password Windows NT hashed passwords {x-nthash} NT-Password Windows NT hashed passwords {lm} LM-Password Windows Lan Manager (LM) passwords. The module tries to be flexible when handling the various password formats. It will automatically handle Base-64 encoded data, hex strings, and binary data, and convert them to a format that the server can use. It is important to understand the difference between the User-Password and Cleartext-Password attributes. The Cleartext-Password attribute is the "known good" password for the user. Simply supplying the Cleartext-Password to the server will result in most authentication meth- ods working. The User-Password attribute is the password as typed in by the user on their private machine. The two are not the same, and should be treated very differently. That is, you should generally not use the User-Password attribute anywhere in the RADIUS configura- tion. For backwards compatibility, there are old configuration parameters which may be work, although we do not recommend using them. SECTIONS
authorize authenticate FILES
/etc/raddb/radiusd.conf SEE ALSO
radiusd(8), radiusd.conf(5) AUTHOR
Alan DeKok <aland@freeradius.org> 6 June 2008 rlm_pap(5)