From: | Michael Meskes <meskes(at)topsystem(dot)de> |
---|---|
To: | scrappy(at)hub(dot)org (The Hermit Hacker) |
Cc: | pgsql-hackers(at)postgresql(dot)org (PostgreSQL Hacker) |
Subject: | Re: pg_user permissions problem (Was: Re: [HACKERS] RE: New ecgp code problem.) |
Date: | 1998-02-19 13:13:06 |
Message-ID: | 199802191313.OAA20992@gauss.topsystem.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The Hermit Hacker writes:
> 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 wasn't able to read data from a DB that I created with the very same user.
But I was able to connect, insert data etc. Why was that possible?
> All we would really need was:
>
> create view all_users as select usename,usesysid from pg_user;
>
> Which psql/odbc/ecgp/jdbc could call instead of what its doing
> now...
ecpg doesn't call anything like that. All I use is some PQ... functions. No
direct access to whatever user permission system we have. So does this have
to be changed in libpq?
Michael
--
Dr. Michael Meskes, Project-Manager | topsystem Systemhaus GmbH
meskes(at)topsystem(dot)de | Europark A2, Adenauerstr. 20
meskes(at)debian(dot)org | 52146 Wuerselen
Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas SARZ | 1998-02-19 13:59:48 | Solution to the pg_user passwd problem !?? (c) |
Previous Message | The Hermit Hacker | 1998-02-19 13:03:00 | RE: [HACKERS] libpgtcl undefined symbol error with pgaccess-0.76 |