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 15:57:09 |
Message-ID: | 3409.1043078229@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:
> Tom Lane sez:
> } Secondary password files aren't supported anymore as of 7.3. If that's
> } not in the release notes, it's a serious oversight :-(
> It certainly isn't mentioned in README or INSTALL. Anyhow, how do I take
> the existing external password file (which has encrypted passwords) and
> put it into the DB?
I'm afraid you don't. The encryption method that was used in external
files was crypt(3), which we're migrating away from for various reasons,
chiefly lack of cross-platform portability. The encryption method
that's now supported in pg_shadow entries is MD5.
I'd counsel issuing temporary new passwords to all your users and
advising them to change them to something of their own choice...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Manfred Koizar | 2003-01-20 16:05:53 | Re: Altering a table - positioning new columns |
Previous Message | Tom Lane | 2003-01-20 15:52:32 | Re: ERROR: No one parent tuple was found |