Password(3pm) User Contributed Perl Documentation Password(3pm)NAME
DBIx::Password - Allows you to create a global password file for DB passwords
SYNOPSIS
use DBIx::Password;
my $dbh = DBIx::Password->connect($user);
my $dbh = DBIx::Password->connect_cached($user);
$dbh->getDriver;
DBIx::Password::getDriver($user);
DBIx::Password::checkVirtualUser($user);
DBIx::Password::clearConfig();
DBIx::Password::readConfig("$ENV{HOME}/.my.secret.file");
DESCRIPTION
Don't you hate keeping track of database passwords and such throughout your scripts? How about the problem of changing those passwords on a
mass scale? This module is one possible solution. It stores all your virtual users and data in /etc/dbix-password.conf. For each user you
need to specify the database module to use, the database connect string, the username and the password. You will have to give a name to
this virtual user. You can add as many as you like.
I would recommend that if you are only using this with web applications that you change the final permissions on this package after it is
installed in site_perl such that only the webserver can read it.
A method called getDriver has been added so that you can determine what driver is being used (handy for working out database indepence
issues).
If you want to find out if the virtual user is valid, you can call the class method checkVirtualUser(). It returns true(1) if the
username is valid, and zero if not.
Once your are done you can use the connect method (or the connect_cache method) that comes with DBIx-Password and just specify one of the
virtual users you defined while making the module.
BTW I learned the bless hack that is used from Apache::DBI so some credit should go to the authors of that module. This is a rewrite of
the module Tangent::DB that I did for slashcode.
If your program does not need the system-wide information stored in the /etc/dbix-password.conf file, you may use the clearConfig() and
readConfig() functions to get the data from another source. At any time, readConfig() may also be used to merge the data from another file
into the currently-loaded configuration.
Hope you enjoy it.
HOME
To find out more information look at: http://www.tangent.org/DBIx-Password/
AUTHOR
Brian Aker, brian@tangent.org
SEE ALSO perl(1). DBI(3).
perl v5.10.0 2009-05-09 Password(3pm)
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)