On Thu, 29 Jan 2009 11:34:00 -0800 (PST) Jeff Frost <jeff@xxxxxxxxxxxxxxxxxxxxxx> 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. > > > On Thu, 29 Jan 2009 13:16:19 -0500 > > Bill Moran <wmoran@xxxxxxxxxxxxxxxxx> wrote: > > > >> In response to rhubbell <Rhubbell@xxxxxxxxxxxx>: > >>> > >>> 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@xxxxxxxxxxxxxxxxxxxxxx> > Frost Consulting, LLC http://www.frostconsultingllc.com/ > Phone: 916-647-6411 FAX: 916-405-4032 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
