| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Including PL/PgSQL by default |
| Date: | 2008-02-21 18:43:27 |
| Message-ID: | 20080221104327.0e34859a@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 21 Feb 2008 13:33:44 -0500
Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> That's not true. The public schema has public UC privs, and always
> has had.
>
This disproves my point how?
> There is nothing surprising (expect possibly to you) here.
>
It is not a surprise to me, you can check the archives I bring it up
often. It is poor implementation and proof that the theoretical
security implications that are being brought up in this thread are far
from the practical reality.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHvcZRATb/zqfZUUQRAvp9AJ9nLf/CW3NvscqJ7zciZWDVil0X8QCghNZY
tiUyxmuWyd4DFjrRZdz2Dao=
=IQdD
-----END PGP SIGNATURE-----
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2008-02-21 18:46:14 | Re: Including PL/PgSQL by default |
| Previous Message | Tom Lane | 2008-02-21 18:38:50 | Re: Including PL/PgSQL by default |