| From: | Marko Kreen <markokr(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, Ricardo Vaz - TCESP <jrvaz(at)tce(dot)sp(dot)gov(dot)br> |
| Subject: | Re: Log of CREATE USER statement |
| Date: | 2005-12-12 13:40:16 |
| Message-ID: | e51f66da0512120540u4a19a674k70ff9b4432a30151@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/9/05, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> Tom Lane wrote:
> > As I said already, if the user wishes the password to be secure, he
> > needs to encrypt it on the client side.
>
> Maybe we should provide a backslash command in psql for secure password
> entry, say, \password [username]. This would then ask for the password
> through a somewhat secure, unlogged channel, encrypt it, and send an
> ALTER ROLE command to the server.
Letting createuser.c hash the password would be the biggest win.
--
marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-12-12 14:02:50 | Re: Reducing relation locking overhead |
| Previous Message | Ricardo Vaz | 2005-12-12 13:20:31 | Re: Log of CREATE USER statement |