| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Zeugswetter Andreas SARZ <Andreas(dot)Zeugswetter(at)telecom(dot)at>, jwieck(at)debis(dot)com, pgsql-hackers(at)hub(dot)org |
| Subject: | Re: AW: [HACKERS] Solution to the pg_user passwd problem !?? (c) |
| Date: | 1998-02-19 17:29:08 |
| Message-ID: | Pine.NEB.3.95.980219122657.17102Q-100000@hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 19 Feb 1998, Bruce Momjian wrote:
> >
> > The command
> > copy pg_user to stdout;
> >
> > will also show the cleartext password and I think it is hard to do a rewrite
> > here,
> > since this would also affect the pg_dump ?
>
> OK, I have committed code that removes the REVOKE from initdb, and does
> not allow them to do any adding or altering of users if there is a
> password involved AND the ACL for pg_user is null. It prints a nice
> message telling them they need to issue the REVOKE command so normal
> users can't read the passwords.
I put the REVOKE back in, with the appropriate rule rewrite...I've
tried it here and it works cleanly, and just masks out the passwd
entry...doesn't compensate for the 'copy' problem, but its better then
expecting the admin to go do the revoke on his own :(
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brett McCormick | 1998-02-19 17:47:47 | Re: [HACKERS] Solution to the pg_user passwd problem !?? (c) |
| Previous Message | Bruce Momjian | 1998-02-19 17:19:59 | Re: AW: [HACKERS] Solution to the pg_user passwd problem !?? (c) |