Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

rlm_pap(5) [centos 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)

Check Out this Related Man Page

rlm_mschap(5)							 FreeRADIUS Module						     rlm_mschap(5)

NAME
rlm_mschap - FreeRADIUS Module DESCRIPTION
The rlm_mschap module provides MS-CHAP and MS-CHAPv2 authentication support. This module validates a user with MS-CHAP or MS-CHAPv2 authentication. If called in Authorize, it will look for MS-CHAP Challenge/Response attributes in the Acess-Request and adds an Auth-Type attribute set to MS-CHAP in the Config-Items list unless Auth-Type has already set. The module can authenticate the MS-CHAP session via plain-text passwords (User-Password attribute), or NT passwords (NT-Password attribute). The module cannot perform authentication against an NT domain. The module also enforces the SMB-Account-Ctrl attribute. See the Samba documentation for the meaning of SMB account control. The module does not read Samba password files. Instead, the fIrlm_passwd module can be used to read a Samba password file, and supply an NT-Password attribute which this module can use. The main configuration items to be aware of are: authtype This is the string used to set the authtype. Normally it should be left to the default value of MS-CHAP. use_mppe Unless this is set to 'no', FreeRADIUS will add MS-CHAP-MPPE-Keys for MS-CHAPv1 and MS-MPPE-Recv-Key/MS-MPPE-Send-Key for MS-CHAPv2. The default is 'yes'. require_encryption If MPPE is enabled, setting this attribute to 'yes' will cause the MS-MPPE-Encryption-Policy attribute to be set to require encryp- tion. The default is 'no'. require_strong If MPPE is enabled, setting this attribute to 'yes' will cause the MS-MPPE-Encryption-Types attribute to be set to require a 128 bit key. The default is 'no'. with_ntdomain_hack Windows clients send User-Name in the form of "DOMAINUser", but send the challenge/response based only on the User portion. Set- ting this value to yes, enables a work-around for this error. The default is 'no'. CONFIGURATION
modules { ... mschap { authtype = MS-CHAP use_mppe = yes } ... } ... authorize { ... mschap ... } ... authenticate { ... mschap ... } SECTIONS
authorization, authentication FILES
/etc/raddb/radiusd.conf SEE ALSO
radiusd(8), radiusd.conf(5) AUTHOR
Chris Parker, cparker@segv.org 13 March 2004 rlm_mschap(5)
Man Page