From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> |
Cc: | "pgadmin-hackers" <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Change password issue |
Date: | 2006-02-17 14:40:07 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E40103E1C1@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
> Sent: 17 February 2006 14:35
> To: Dave Page
> Cc: pgadmin-hackers
> Subject: Re: [pgadmin-hackers] Change password issue
>
> Dave Page wrote:
> > I spotted an issue with the change password dialogue today;
> if you have
> > connected using trust authentication, or a password in
> pgpass.conf, then
> > there is no way to change the password because the pgServer object
> > doesn't know what the original one is.
> >
> > The simple fix would be to remove the 'enter old password'
> requirement,
> > but that just doesn't feel right. For pgpass connections we
> could try to
> > retrieve the password from the file, but there is no way for trusted
> > connections that I can see.
> >
> > Thoughts?
>
> On the TODO list.
It is? Can't see it for looking :-(
> As soon as we encrypt the password to
> create the SQL
> we can ask for the password, encrypt and check against
> pg_authid ourselves.
Yeah, that sounds reasonable.
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2006-02-17 15:22:13 | Re: Change password issue |
Previous Message | Dave Page | 2006-02-17 13:16:20 | Re: Norwegian Translation |