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

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

From: Bill Moran <wmoran(at)potentialtech(dot)com>
To: rhubbell <Rhubbell(at)iHubbell(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: md5 doesn't work (Was Re: Pet Peeves?)
Date: 2009-01-29 19:56:18
Message-ID: 20090129145618.7e1a9cc9.wmoran@potentialtech.com (view raw or flat)
Thread:
Lists: pgsql-general
In response to rhubbell <Rhubbell(at)iHubbell(dot)com>:

> On Thu, 29 Jan 2009 11:34:00 -0800 (PST)
> Jeff Frost <jeff(at)frostconsultingllc(dot)com> wrote:
> 
> > 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.
> 
> Yeah, yeah, did all that, didn't work. Sorry, still a "Pet Peeve". (^;
> While you mention it, another "Pet Peeve" was the use of ident. Yikes.

_My_ point was that a broken md5 (which is still under debate) doesn't
force you to use trust.  There are other auth options like crypt and
password.

-- 
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/

In response to

pgsql-general by date

Next:From: Alan HodgsonDate: 2009-01-29 19:59:32
Subject: Re: md5 doesn't work (Was Re: Pet Peeves?)
Previous:From: Mark StylesDate: 2009-01-29 19:55:45
Subject: Re: Changing owner of pg_toast tables

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