From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | gss+pg(at)cs(dot)brown(dot)edu |
Cc: | PostgreSQL general mailing list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: passwords and 7.3 |
Date: | 2003-01-20 16:30:40 |
Message-ID: | 3682.1043080240@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Gregory Seidman <gss+pg(at)cs(dot)brown(dot)edu> writes:
> Incidentally, how do I make an md5 password? I assume the authentication
> method in pg_hba.conf has to be set to md5, but how do I encrypt the
> password to put in the passwd field in pg_shadow?
The system does it for you, if you specify ENCRYPTED in the CREATE or
ALTER USER command that sets the password. There is also a
postgresql.conf option that makes ENCRYPTED the default behavior of
these commands --- which we did not turn on for 7.3, but it will be on
by default for 7.4, IIRC.
As of current sources, an MD5-stored password can be used with either
password or md5 auth protocol --- but AFAICS the only reason you'd want
to use password (cleartext) protocol would be backwards compatibility
with ancient client libraries. (Due to an oversight, 7.3 release
required you to use md5 protocol with an md5 password; this is fixed for
7.3.2, but I don't recall whether it got into 7.3.1 or not.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | mike | 2003-01-20 16:59:26 | readline configure error again |
Previous Message | Tom Lane | 2003-01-20 16:20:51 | Re: Altering a table - positioning new columns |