Skip site navigation (1) Skip section navigation (2)

Re: bug in pgadmin III

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>,Michiel Lange <Michiel_Lange(at)actuera(dot)com>,pgadmin-support(at)postgresql(dot)org
Subject: Re: bug in pgadmin III
Date: 2003-11-18 01:19:26
Message-ID: 3FB9739E.6050208@familyhealth.com.au (view raw or flat)
Thread:
Lists: pgadmin-support
>>If you know how to encrypt the password, we certainly could 
>>supply the option to enter it that way...
> 
> 
> It's just an md5 hash prefixed with 'md5' isn't it?

???

Don't you just go ALTER USER blah ENCRYPTED PASSWORD 'asdf';

And postgres itself will encrypt it for you.

Your SQL view should show whatever PostgreSQL's pg_dump shows I think.

Chris


In response to

pgadmin-support by date

Next:From: Dave PageDate: 2003-11-18 08:04:29
Subject: Re: bug in pgadmin III
Previous:From: Keith C. PerryDate: 2003-11-17 21:29:07
Subject: Re: Query tool and SSL connections

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group