Re: Known but bad behavior with alter user?
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Stephen Frost <sfrost(at)snowman(dot)net>
- Cc: "Joshua D. Drake" <jd(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: Known but bad behavior with alter user?
- Date: Fri, 24 Mar 2006 13:13:29 -0500
- Message-id: <6207(dot)1143224009(at)sss(dot)pgh(dot)pa(dot)us>
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Joshua D. Drake (jd(at)commandprompt(dot)com) wrote:
>> template1=3D# alter user foo rename to bar;
>> NOTICE: MD5 password cleared because of role rename
>> Now we have to reset the password.. which seems an extra
>> step that shouldn't be required.
> Wouldn't this be because the username is used as the salt for MD5 and so
> there's no way to update the password because the system doesn't know
> the original password?
Yeah. This isn't changing unless you have an alternative that's not
worse (ie, doesn't defeat the purpose of storing an encrypted password).
regards, tom lane
Home |
Main Index |
Thread Index