postgresql

History

Tom Lane f85f43dfb5 Backend support for autocommit removed, per recent discussions. The only remnant of this failed experiment is that the server will take SET AUTOCOMMIT TO ON. Still TODO: provide some client-side autocommit logic in libpq.		2003-05-14 03:26:03 +00:00
..
Makefile	Might need to link with -lcrypt.	2002-10-21 18:55:10 +00:00
README.chkpass	Initial checkin of a contributed type that handles passwords efficiently.	2001-05-03 12:32:13 +00:00
chkpass.c	Add missing semicolons to a few PG_FUNCTION_INFO_V1 calls.	2002-10-26 15:01:01 +00:00
chkpass.sql.in	Backend support for autocommit removed, per recent discussions. The	2003-05-14 03:26:03 +00:00

README.chkpass

$Header: /cvsroot/pgsql/contrib/chkpass/Attic/README.chkpass,v 1.1 2001/05/03 12:32:13 darcy Exp $

Chkpass is a password type that is automatically checked and converted upon
entry.  It is stored encrypted.  To compare, simply compare agains a clear
text password and the comparison function will encrypt it before comparing.
It also returns an error if the code determines that the password is easily
crackable.  This is currently a stub that does nothing.

I haven't worried about making this type indexable.  I doubt that anyone
would ever need to sort a file in order of encrypted password.

If you precede the string with a colon, the encryption and checking are
skipped so that you can enter existing passwords into the field.

On output, a colon is prepended.  This makes it possible to dump and reload
passwords without re-encrypting them.  If you want the password (encrypted)
without the colon then use the raw() function.  This allows you to use the
type with things like Apache's Auth_PostgreSQL module.

D'Arcy J.M. Cain
darcy@druid.net