postgresql

mirror of https://git.postgresql.org/git/postgresql.git synced 2024-12-03 08:00:21 +08:00

History

Tom Lane b663f3443b Add a bunch of pseudo-types to replace the behavior formerly associated with OPAQUE, as per recent pghackers discussion. I still want to do some more work on the 'cstring' pseudo-type, but I'm going to commit the bulk of the changes now before the tree starts shifting under me ...		2002-08-22 00:01:51 +00:00
..
chkpass.c	Fix warning	2001-12-19 18:49:24 +00:00
chkpass.sql.in	Add a bunch of pseudo-types to replace the behavior formerly associated	2002-08-22 00:01:51 +00:00
Makefile	To fix the perpetually broken makefiles in the contrib tree, I have	2001-09-06 10:49:30 +00:00
README.chkpass

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