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(dot) Drake" <jd(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Known but bad behavior with alter user?
Date: 2006-03-24 18:13:29
Message-ID: 6207.1143224009@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2006-03-24 18:27:10 Re: Role incompatibilities
Previous Message Stephen Frost 2006-03-24 18:02:27 Re: Known but bad behavior with alter user?