# password: Authentication is done by matching a password supplied
# in clear by the host. If no AUTH_ARGUMENT is used, the
# password is compared with the user's entry in the
# pg_shadow table.
It seems to me that this doesn't work for encrypted passwords stored in
pg_shadow? The crypt: entry specifically mentions not storing encrypted
passwords.. Just checking here, as it's a windoze box connecting with ODBC
that has the problem, all the unix boxen are happy with md5 and encrypted
passwords, so there could be many other causes for it to be unhappy..
Cheers,
Patrick
