<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<meta name="GENERATOR"
content="Mozilla/4.05 [en] (X11; I; Linux 2.0.34 i686) [Netscape]">
<title>Module mod_auth_pgsql PostgreSQL authentication module fro
Apache web server</title>
</head>
<body>
<h1>Apache2 Module mod_auth_pgsql</h1>
<h2> PostgreSQL Authentication </h2>
This module allows user authentication (and can log authethication
requests) against information stored in a <a
href="http://www.postgresql.org/"> PostgreSQL</a> database. PostgreSQL
is a public domain SQL database.
<ul>
<li>Authentication</li>
</ul>
<pre> One database, and one (or two) tables. One table holds the username and the encryped (or plain) password.<br> The other table holds the username and the names of the group to which the user belongs. <br> It is possible to have username, groupname and password in the same table. <br></pre>
<ul>
<li>Access Logging</li>
</ul>
<pre> Every authentication access is logged in the same database of the authentication table, but in different table.<br> User name and date of the request are logged.<br> As option, it can log <i>password, </i><i>ip address</i>, <i>request lin</i>e.<br></pre>
<p><br>
</p>
<p><br>
This page documents version 2.0.0 (2003 01 30) of mod_auth_pgsql
require Apache >= 2.0.40 and PostreSQL >= 7.x <br>
If you need to authenticate with Apache 1.3.x please use the old
version (0.9.12), this one will not work.<br>
</p>
<p><br>
Home Page <a href="http://www.giuseppetanzilli.it/mod_auth_pgsql2/">http://www.giuseppetanzilli.it/mod_auth_pgsql2/</a><br>
</p>
<p>Old module for Apache 1.3 : <a
href="http://www.giuseppetanzilli.it/mod_auth_pgsql/">http://www.giuseppetanzilli.it/mod_auth_pgsql/</a><br>
</p>
<p><br>
</p>
<p><a href="#Directives">Module Directives </a> | <a href="#Download">
Download </a> | <a href="#compile">Compilation & Installation
Notes</a> | <a href="#example">Example</a> | <a href="#notes">Technical
Notes</a> |<a href="#Changelog"> Changelog</a> </p>
<h2><a name="Directives"></a> Directives</h2>
<ul>
<li><a href="#host">Auth_PG_host</a> </li>
<li><a href="#port">Auth_PG_port</a> </li>
<li><a href="#options">Auth_PG_options</a> </li>
<li><a href="#pwd_table">Auth_PG_database</a> </li>
<li><a href="#PGuser">Auth_PG_user</a> </li>
<li><a href="PGpwd">Auth_PG_pwd</a> </li>
<li><a href="#grp_table">Auth_PG_pwd_table</a> </li>
<li><a href="#uid_field">Auth_PG_grp_table</a> </li>
<li><a href="#uid_field">Auth_PG_uid_field</a> </li>
<li><a href="#pwd_field">Auth_PG_pwd_field</a> </li>
<li><a href="#gid_field">Auth_PG_gid_field</a> </li>
<li><a href="#nopasswd">Auth_PG_nopasswd</a> </li>
<li><a href="#authoritative">Auth_PG_authoritative</a> </li>
<li><a href="#lowercaseuid">Auth_PG_lowercase_uid</a> </li>
<li><a href="#uppercaseuid">Auth_PG_uppercase_uid</a></li>
<li><a href="#pwd_ignore_case">Auth_PG_pwd_ignore_case</a><br>
</li>
<li><a href="#encrypted">Auth_PG_encrypted</a> </li>
<li><a href="#hash_type">Auth_PG_hash_type</a> <br>
</li>
<li><a href="#pwd_whereclause">Auth_PG_pwd_whereclause</a> </li>
<li><a href="#grp_whereclause">Auth_PG_grp_whereclause</a></li>
<li><a href="#cache_passwords">Auth_PG_cache_passwords</a><br>
</li>
<li><a href="#log_table">Auth_PG_log_table</a> </li>
<li><a href="#log_uname_field">Auth_PG_log_uname_field</a> </li>
<li><a href="#log_date_field">Auth_PG_log_date_field</a> </li>
<li><a href="#log_uri_field">Auth_PG_log_uri_field</a> </li>
<li><a href="#log_addrs_field">Auth_PG_log_addrs_field</a> </li>
<li><a href="#log_pwd_field">Auth_PG_log_pwd_field</a> </li>
</ul>
<hr>
<h2><a name="host"></a> Auth_PG_host</h2>
<b>Syntax:</b> Auth_PG_host <i>hostname</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>Specifies the host on which the <b>postmaster</b> is running. The
effective uid of the server should be allowed access,
otherwise a trusted user or user with password must be
specified. </p>
<h2><a name="port"></a> Auth_PG_port</h2>
<b>Syntax:</b> Auth_PG_port <i>port number</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>Specifies the TCP/IP port number at which the <b>postmaster</b> can
be found. </p>
<h2><a name="options"></a> Auth_PG_options</h2>
<b>Syntax:</b> Auth_PG_options <i>option string</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>Specifies an option string to be passed to the postgreSQL backend
process. Refer to the PostgreSQL user manual for a
description of the available options. </p>
<h2><a name="database"></a> Auth_PG_database</h2>
<b>Syntax:</b> Auth_PG_database <i>database name</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>Specifies the name of the database that stores the authentication
information.<br>
<br>
</p>
<h2><a name="PGuser"></a> Auth_PG_user<br>
</h2>
<b>Syntax:</b> Auth_PG_user <i>username</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension <br>
<br>
Specifies the database username who access the PostgreSQL,
should have read access on all authetication tables, and write
access on all the log tables (if used).<br>
Needed if the user who make the quey is differrent from the
user runnig apache, or if the posmater is on a different
server and you must autheticate with password<br>
<h2><a name="PGpwd"></a> Auth_PG_pwd</h2>
<p><b>Syntax:</b> Auth_PG_pwd <i>password</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension <br>
<br>
Specifies the user password for the user who access the
PostgreSQL.<br>
Needed if the user specified with Auth_PG_user is not trusted.<br>
</p>
<p><br>
</p>
<h2><a name="pwd_table"></a> Auth_PG_pwd_table</h2>
<b>Syntax:</b> Auth_PG_pwd_table <i>relation name</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>Gives the name of the relation which contains the username and
password information.<br>
See Auth_PG_encrypted, by default the password is encrypted.<br>
</p>
<h2><a name="grp_table"></a> Auth_PG_grp_table</h2>
<b>Syntax:</b> Auth_PG_grp_table <i>relation name</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>Gives the name of the relation which contains the username and group
information. This can be the same table specified with
Auth_PG_pwd_table. This directive is only necessary if you
want to authenticate by user groups. A user within multiple
groups has therefore multiple entries. </p>
<h2><a name="uid_field"></a> Auth_PG_uid_field</h2>
<b>Syntax:</b> Auth_PG_uid_field <i>attribute name</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>Specifies the attribute name of the field containing the user name
in the Auth_PG_pwd_table relation. </p>
<h2><a name="pwd_field"></a> Auth_PG_pwd_field</h2>
<b>Syntax:</b> Auth_PG_pwd_field <i>attribute name</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>Specifies the attribute name of the field containing the encrypted
(see Auth_PG_encrypted) password in the Auth_PGpwd_table
relation.<br>
Please remember to use field of type varchar, not char for the password.<br>
</p>
<h2><a name="gid_field"></a> Auth_PG_gid_field</h2>
<b>Syntax:</b> Auth_PG_gid_field <i>attribute name</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>Specifies the attribute name of the field containing the group name
in the Auth_PG_grp_table relation. This directive is
only necessary if you want to authenticate by user groups. </p>
<h2><a name="nopasswd"></a> Auth_PG_nopasswd</h2>
<b>Syntax:</b> Auth_PG_nopasswd <i>on</i> or <i>off</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>This option is off by default. Turning it on will cause a user to be
validated when their password field is empty. The
password entered will be ignored. Exercise caution when
turning this on. </p>
<h2><a name="authoritative"></a> Auth_PG_authoritative</h2>
<b>Syntax:</b> Auth_PG_authoritative <i>on</i> or <i>off</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>This option is on by default. Turning it off will cause low level
errors such a user not being found or a simple
configuration error to fall through to other authentication
directives which may be defined for this area. For example, if
a parent directory has another authorization scheme and a user
name is not found for the PostgreSQL scheme, the parent directory
scheme will be given the chance to try and authenticate the user.
Exercise caution when turning this option off. It can be a security
risk. Can be used to use two authentication schemes for the same
dir. </p>
<h2><a name="lowercaseuid"></a> Auth_PG_lowercase_uid</h2>
<b>Syntax:</b> Auth_PG_lowercase_uid <i>on</i> or <i>off</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>This option is off by default. Controls whether this module converts
user UIDs to lowercase before looking them up. When turned on this
does not affect the case of the original user ID should this module
decline to authenticate and a lower level is called.</p>
<h2><a name="uppercaseuid"></a> Auth_PG_uppercase_uid</h2>
<b>Syntax:</b> Auth_PG_uppercase_uid <i>on</i> or <i>off</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>This option is off by default. Controls whether this module converts
user UIDs to uppercase before looking them up. When turned on this
does not affect the case of the original user ID should this module
decline to authenticate and a lower level is called.</p>
<h2><a name="pwd_ignore_case"></a> Auth_PG_pwd_ignore_case</h2>
<b>Syntax:</b> Auth_PG_pwd_ignore_case <i>on</i> or <i>off</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>This option is off by default. Controls whether this module ignore
the upper/lowercase of password from user, when looking up clear text
password from db. </p>
<h2><a name="encrypted"></a> Auth_PG_encrypted</h2>
<b>Syntax:</b> Auth_PG_encrypted <i>on</i> or <i>off</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>Defaults to on. Controls weather this module expects passwords in
the database to be encrypted or not. When turned off, you can use
unencrypted passwords in your database. Exercise caution when deciding
to turn this off!</p>
<p><br>
</p>
<h2><a name="hash_type"></a> Auth_PG_hash_type</h2>
<b>Syntax:</b> Auth_PG_hash_type CRYPT or MD5 or BASE64<br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>Set the encryption type for the password stored in the database.<br>
Defaults to CRYPT. </p>
<p><br>
</p>
<h2><a name="pwd_whereclause"></a> Auth_PG_pwd_whereclause</h2>
<b>Syntax:</b> Auth_PG_pwd_whereclause <i>SQL fragment</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>This option allows you to exercise greater control over the SQL code
used to retrieve the user name and password from the
database. You can use this to search for the username using
more attributes in the table than the pwd_field. </p>
<p>The basic SQL statement used to retrieve a user's password for
checking looks like this: </p>
<ul>
select <i><pwd_field></i> from <i><pwd_table></i> where <i>
<uid_field></i> ='<i><remote_user></i> '
</ul>
<p>The pwd_whereclause will be added to the end of this statement and
must fit logically. <em>The where clause must be
double quoted, with initial space .</em></p>
<p>Example: </p>
<pre> Auth_PG_pwd_whereclause " and access_level > 100 "</pre>
<p> </p>
<h2><a name="grp_whereclause"></a> Auth_PG_grp_whereclause</h2>
<b>Syntax:</b> Auth_PG_grp_whereclause <i>SQL fragment</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension
<p>This option allows you to exercise greater control over the SQL code
used to retrieve the group name and corresponding user
from the database. You can use this to search for the group
name using more attributes in the table than the gid_field. </p>
<p>The basic SQL statement used to retrieve a group name and user name
for checking looks like this: </p>
<ul>
select <i><uid_field></i> from <i><grp_table></i> where <i>
<gid_field></i> ='<i><required group></i> '
</ul>
The gid_whereclause will be added to the end of this statement
and must fit logically. <em>The where clause must be double
quoted.<br>
<br>
<br>
</em>
<h2><a name="log_table"></a> Auth_PG_cache_passwords</h2>
<b>Syntax:</b> Auth_PG_cache_passwords on | off<br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension<br>
<br>
Enable password caching, default is off. <br>
The cache table is local to the directory, will be cleaned when full,
default size is 50.<br>
<br>
<h2><a name="log_table"></a> Auth_PG_log_table</h2>
<b>Syntax:</b> Auth_PG_log_table <i>table name</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension<br>
<br>
Specifies the table where logging information will go, the user
need write access to this table.<br>
Required for logging.<br>
<br>
<h2><a name="log_uname_field"></a> Auth_PG_log_uname_field</h2>
<b>Syntax:</b> Auth_PG_log_uname_field <i>fieldname</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension<br>
<br>
Specifies the fieldname where the username will be saved.<br>
Required for logging.<br>
<br>
<h2><a name="log_date_field"></a> Auth_PG_log_date_field</h2>
<b>Syntax:</b> Auth_PG_log_date_field <i>fieldname</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension<br>
<br>
Specifies the fieldname where the date will be saved.<br>
Required for logging.<br>
<br>
<h2><a name="log_uri_field"></a> Auth_PG_log_uri_field</h2>
<b>Syntax:</b> Auth_PG_uri_field <i>fieldname</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension<br>
<br>
Specifies the fieldname where the request string will be saved.<br>
Optional for logging.<br>
<h2><a name="log_addrs_field"></a> Auth_PG_log_addrs_field</h2>
<b>Syntax:</b> Auth_PG_addrs_field <i>fieldname</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension<br>
<br>
Specifies the fieldname where the IP address will be saved.<br>
Optional for logging.<br>
<h2><a name="log_pwd_field"></a> Auth_PG_log_pwd_field</h2>
<b>Syntax:</b> Auth_PG_pwd_field <i>fieldname</i><br>
<b>Context:</b> directory, .htaccess <br>
<b>Override:</b> AuthConfig <br>
<b>Status:</b> Extension<br>
<br>
Specifies the fileld name where the password used to authenticate
will be saved.<br>
<b>Note: the password will be saved in clear text</b><br>
Optional for logging.<br>
<br>
<br>
<hr>
<h2><a name="example"></a> Example</h2>
Here is an example <b>.htaccess</b> file you might use to enable
PostgreSQL authentication:
<pre><br>PostgreSQL trusted user:<br><br> AuthName "My PostgreSQL Authenticator"<br> AuthType basic<br><br> Auth_PG_host localhost<br> Auth_PG_port 5432<br> Auth_PG_user postgres<br> Auth_PG_database www<br> Auth_PG_pwd_table valid_users<br> Auth_PG_uid_field user<br> Auth_PG_pwd_field password<br><br> <LIMIT GET POST><br> require valid-user<br> </LIMIT><br><br>PostgreSQL trusted user, select only users with access_level > 100:<br><br> AuthName "My PostgreSQL Authenticator"<br> AuthType basic<br><br> Auth_PG_host localhost<br> Auth_PG_port 5432<br> Auth_PG_user postgres<br> Auth_PG_database www<br> Auth_PG_pwd_table valid_users<br> Auth_PG_uid_field user<br> Auth_PG_pwd_field password<br> Auth_PG_pwd_whereclause " and access_level > 100 "<br><br> <LIMIT GET POST><br> require valid-user<br> </LIMIT><br><br>PostgreSQL user with password authentication, with logging:<br><br> AuthName "My PostgreSQL Authenticator"<br> AuthType basic<br><br> Auth_PG_host someserver.somenet<br> Auth_PG_port 5432<br> Auth_PG_user postgres<br> Auth_PG_pwd xxxxxxx<br> Auth_PG_database www<br> Auth_PG_pwd_table valid_users<br> Auth_PG_uid_field user<br> Auth_PG_pwd_field password<br> Auth_PG_log_table access_log<br> Auth_PG_log_uname_field login<br> Auth_PG_log_date_field date<br> Auth_PG_log_uri_field request<br> Auth_PG_log_addrs_field ip_address<br><br><br> <LIMIT GET POST><br> require valid-user<br> </LIMIT><br><br><br><br><br><br></pre>
<h2><a name="notes"></a> Technical Notes</h2>
<ul>
<li> If the SQL statement used to retrieve the user or group name
returns more than one tuple, it is considered an error.
If this is likely to happen, use Auth_PG_pwd_whereclause
and Auth_PG_grp_whereclause to create a query that will only
return one tuple.<br>
</li>
</ul>
<br>
<br>
<br>
<br>
<h2><a name="Download"></a> Download </h2>
<ul>
<li> Latest release:<br>
<a href="http://www.giuseppetanzilli.it/mod_auth_pgsql2/dist/">
http://www.giuseppetanzilli.it</a> <a
href="http://www.giuseppetanzilli.it/mod_auth_pgsql2/dist/">
/mod_auth_pgsql2/dist/</a> </li>
<li>Homepage and Documentation:<br>
<a href="http://www.giuseppetanzilli.it/mod_auth_pgsql2/">http://www.giuseppetanzilli.it/mod_auth_pgsql2</a> </li>
</ul>
<br>
<br>
<br>
<br>
<h2><a name="compile"></a> Compilation & Installation Notes</h2>
<b>From the INSTALL file:</b>
<pre>PXS DSO Install:<br> - untar mod_auth_pgsql <br> cd /usr/local/src<br> tar zxf mod_auth_pgsql-2.0.x.tar.gz<br> cd mod_auth_pgsql-2.0.x<br> - make & install as DSO<br> <br> /usr/local/apache2/bin/apxs -i -a -c -I /usr/local/pgsql/include -L /usr/local/pgsql/lib -lpq mod_auth_pgsql.c<br> <br> <br><br>STATIC Install<br><br><br> - untar mod_auth_pgsql <br> cd /usr/local/src<br> tar zxf mod_auth_pgsql-2.0.x.tar.gz<br><br> - untar apache source and run ./configure from the apache source dir<br> cd /usr/local/src<br> tar zxf httpd-2.0.x.tar.gz<br> <br> cd httpd-2.0.x<br> ./configure --with-module=aaa:../mod_auth_pgsql-2.0.x/mod_auth_pgsql.c<br><br> - edit config_vars.mk<br> vi build/config_vars.mk <br> add "-I/usr/local/pgsql/include" to the end of EXTRA_INCLUDES <br> add "-lpq -L/usr/local/pgsql/lib" to the end of EXTRA_LIBS<br> <br> NOTE: they have to be the last in the line, otherwise we get conflicts between pgsql & apache includes<br> NOTE2: there is a way to do it in a better way (without vi ) ? <br> <br> - make & install <br> make<br> make install<br> <br><br><br><br><br></pre>
<h2><a name="Changelog"></a> Changelog </h2>
Version 0.0 (Feb 1996) First release (adaptation from
mod_auth_msql.c v0.5)<br>
mod_auth_msql.c was written by Dirk.vanGulik@jrc.it;<br>
0.1 (Mar 1996) Correct PGgid_field command<br>
0.2 (Mar 1996) Added use and
Auth_PGgrp_whereclause<br>
0.3 (May 1996) Some sundry patches to fix
grp_whereclause and some compilation<br>
issues. Thanks to Randy Terbrush.<br>
0.4 (Jun 1996) Got rid of pg_set_string_slot,
use the stock function in http_config.c<br>
Made Auth_PGoptions take an actual string argument.<br>
Fixed some logical sillyness in check_auth<br>
Made command error strings more reasonable.<br>
Try to weed out possibility of function names conflicting<br>
with other 3rd party modules.<br>
Added Auth_PG_authorative directive<br>
Added Auth_PG_enrypted directive<br>
0.5 (Dec 1996) Some cosmetic changes to
make apache 1.2 happy.<br>
Added correctly spelled Auth_PG_Authoratative command.<br>
0.6 (13 July 1998) Renamed to
mod_auth_pgsql <br>
Some changes just to make it compile under
apache 1.3<br>
tested on apache 1.3 postgreSQL 6.4<br>
Giuseppe Tanzilli g.tanzilli@eurolink.it<br>
0.7 (11 November 1998) <br>
Some little changes just to make it compile
in<br>
Apache 1.3.3 & PostgreSQL 6.4<br>
the Where clause commands now need double
quote<br>
<br>
0.7.1 02 March 1999<br>
- now
compile with Apache 1.3.3 & PostgreSQL 6.4<br>
- now
configuration tag in apache for where clause need double quote <br>
- use the
APACI configuration script<br>
-
APACI-Configuration with 1.3.4, additional-Server-Info-String<br>
<br>
0.7.2 25 June 1999<br>
- now
compile with Apache 1.3.6 & PostgreSQL 6.5<br>
<br>
0.8.0 8 August 1999<br>
- now
apache 1.3.1 and PostgreSQL 6.5 are needed<br>
Added
options to access authenticated database<br>
Added
options to log the authentication requests <br>
<br>
<br>
0.9.0 1999-10-03 (Tollef Fog Heen
<tollef@add.no>)<br>
- tested
on apache 1.3.9 and PostgreSQL 6.5.3<br>
-
added autoconf-script<br>
-
shared module support<br>
<br>
0.9.1 2000-03-31 (Tollef Fog Heen
<tollef@add.no>)<br>
- fixed some minor bugs
related to autoconf (we don't need expat)<br>
<br>
0.9.2 2000-05-21 (Hayato UENOHARA
<uenohara@ueda.info.waseda.ac.jp>)<br>
- Original by Matthias
Eckermann <eckerman@lrz.uni-muenchen.de><br>
- I only copied it from
a lost branch version 0.7.1 (gone for some reason)<br>
- So all credit goes to
Matthias :-)<br>
- added
'AUTH_PGSQL_VERSION' & 'pg_auth_init_handler'<br>
<br>
0.9.5 2000-06-04 (Voloda
<vladimir.kloz@dtg.cz>)<br>
- added options Auth_PGuser, Auth_PGpwd <br>
<br>
0.9.6 2001-08-27 (Giuseppe Tanzilli
<info@giuseppetanzilli.it>)<br>
- ported
configure & install to Apache 1.3.20 and PostgreSQL 7.1.x<br>
-
replaced sprintf with snprintf thanks to Erik Rossen
<rossen@freesurf.ch><br>
-
changed some directive names to make all them like Auth_PG_*<br>
UPDATE YOUR CONFIG FILES<br>
-
Added Logging feature from 0.8 source<br>
-
Check input string from user, to deny sql string attack, see report:<br>
http://cert.uni-stuttgart.de/advisories/apache_auth.php <br>
-
Updated html documentation<br>
<br>
0.9.7 2001-09-02 (Giuseppe
Tanzilli <info@giuseppetanzilli.it>)<br>
- fix Auth_PG_pwd_whereclause &
Auth_PG_grp_whereclause <br>
0.9.8 2001-09-03 (
Andrei Nigmatulin <anight@mail.ru>)<br>
- Added Auth_PG_hash_type, now we support crypt and md5
password hash method <br>
0.9.9 2001-09-25
(Giuseppe Tanzilli <info@giuseppetanzilli.it>)<br>
- fix security problem<br>
- added password caching, default is off,
please check it and report by mail<br>
it will be useful for hi load
sites<br>
0.9.10 2001-10-11 (Giuseppe
Tanzilli <info@giuseppetanzilli.it>)<br>
- fix MD5 auth failures in some cases<br>
0.9.11 2001-11-20 (Giuseppe Tanzilli
<info@giuseppetanzilli.it>)<br>
- security fix: string buffers
Sebastian Krahmer <krahmer@suse.de> and Andreas
Hasenack <andreas@conectiva.com.br><br>
- added Auth_PG_lowercase_uid option
(Bernard Quatermass <bernard@quatermass.co.uk>)<br>
- added Auth_PG_uppercase_uid option <br>
- added --with-pgsql-lib=<dir> and
--with-pgsql-include=<dir> to configure, to make happy debian
users<br>
0.9.12 2002-01-11 (Giuseppe
Tanzilli <info@giuseppetanzilli.it>)<br>
- small fix for
Auth_PG_uppercase_uid/Auth_PG_lowercase_uid<br>
- added Auth_PG_pwd_ignore_case option <br>
2.0.0 2003-01-30
(Giuseppe Tanzilli <info@giuseppetanzilli.it>)<br>
- ported to Apache 2.0<br>
- fixes from Gary Benson
<gbenson@redhat.com> <br>
- fixes from Guenter Knauf
<info@gknw.de><br>
- added debug feature, compile time
option, do not use it on production systems<br>
- added Auth_PG_grp_user_field<br>
- renamed Auth_PG_gid_field to
Auth_PG_grp_group_field<br>
- added BASE64 support, thanks to
Norikatsu Shigemura <n-shigemura@ensure-tech.co.jp><br>
- now we reuse database
connection, 2x speedup !! <br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>
