Skip site navigation (1) Skip section navigation (2)

md5 doesn't work (Was Re: Pet Peeves?)

From: Jeff Frost <jeff(at)frostconsultingllc(dot)com>
To: rhubbell <Rhubbell(at)iHubbell(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: md5 doesn't work (Was Re: Pet Peeves?)
Date: 2009-01-29 19:34:00
Message-ID: Pine.LNX.4.64.0901291132160.17834@discord (view raw, whole thread or download thread mbox)
Lists: pgsql-general
On Thu, 29 Jan 2009, rhubbell wrote:

> Umm, because md5 doesn't work and trust does work.

Generally this is because you haven't yet set a password for the postgres 
user.  You have to set a password for at least the postgres user via ALTER 
ROLE while you've still got it set to trust or ident before changing to md5.

> 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).

Jeff Frost, Owner 	<jeff(at)frostconsultingllc(dot)com>
Frost Consulting, LLC
Phone: 916-647-6411	FAX: 916-405-4032

In response to


pgsql-general by date

Next:From: rhubbellDate: 2009-01-29 19:41:23
Subject: Re: md5 doesn't work (Was Re: Pet Peeves?)
Previous:From: Alan HodgsonDate: 2009-01-29 19:32:20
Subject: Re: Pet Peeves?

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group