| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | scrappy(at)hub(dot)org (The Hermit Hacker) |
| Cc: | meskes(at)topsystem(dot)de, emkxp01(at)mtcc(dot)demon(dot)co(dot)uk, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: pg_user permissions problem (Was: Re: [HACKERS] RE: New ecgp code problem.) |
| Date: | 1998-02-19 14:31:50 |
| Message-ID: | 199802191431.JAA18146@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I spent time with Julie last night working on this, and the
> problem comes back down to "pg_user: Permission Denied"...
>
> I think this is a high priority problem, since it affects so many
> things.
>
> What is the chance of (how hard would it be to?) having a hard
> coded view setup that overrides the permissions lock on pg_user? At what
> point is the lock implemented, software level, or file system?
>
I believe the only way to fix it at this point is to remove the REVOKE
pg_user from initdb, and add a check in user.c to make sure the
permissions on pg_user are not NULL if they try and use passwords.
--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-02-19 14:50:32 | Re: [HACKERS] Solution to the pg_user passwd problem !?? (c) |
| Previous Message | Bruce Momjian | 1998-02-19 14:24:36 | Re: [HACKERS] Shared memory corruption? |