From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Removing a user's password |
Date: | 2003-05-26 18:47:40 |
Message-ID: | 4307.1053974860@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> If you set VALID UNTIL to 'now' (or sometime in the past), you've
>> effectively prevented him from logging in with the password ---
>> more effectively than setting the password to NULL, since if the
>> user is still logged in he can just undo that. I don't think we
>> really need to do anything more here.
> Well, can they undo the VALID UNTIL too?
No: a non-superuser can only set his password, not any other fields of
his pg_shadow entry.
> I think at a minimum we need
> to document the proper procedure for removing a password. I see NULL as
> a more logical way of removing the password rather than playing with
> VALID UNTIL.
It may be more logical, but it doesn't work as well.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-05-26 18:55:59 | Re: Removing a user's password |
Previous Message | Bruce Momjian | 2003-05-26 18:36:34 | Re: Changing behavior of BEGIN...sleep...do something...COMMIT |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-05-26 18:55:59 | Re: Removing a user's password |
Previous Message | Bruce Momjian | 2003-05-26 18:32:33 | Re: [HACKERS] ECPG thread-safety |