Umm, because md5 doesn't work and trust does work.
On Thu, 29 Jan 2009 13:16:19 -0500
Bill Moran <wmoran(at)potentialtech(dot)com> wrote:
> In response to rhubbell <Rhubbell(at)iHubbell(dot)com>:
> > I'm a new user to PostgreSQL so mine's fresh from doing an install recently.
> > In /etc/postgresql/8.3/main/pg_hba.conf
> > # METHOD can be "trust", "reject", "md5", "crypt", "password", "gss", "sspi",
> > # "krb5", "ident", "pam" or "ldap". Note that "password" sends passwords
> > # in clear text; "md5" is preferred since it sends encrypted passwords.
> > So I chose md5 but it will not work, seems like a basic thing. So I am
> > forced to use "trust".
> How on earth does failure of md5 to work force you to use trust?
> How about crypt or password (password is pretty darn simple to set up).
> Bill Moran
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
In response to
pgsql-general by date
|Next:||From: rhubbell||Date: 2009-01-29 19:23:27|
|Subject: Re: Pet Peeves?|
|Previous:||From: Michael Monnerie||Date: 2009-01-29 19:14:28|
|Subject: Re: [GENERAL] Encoding problem using pg_dumpall|