Might as well just get rid of that one; Peter's right about the security hole.
The simplest fix I see is to allow SET AUTHORIZATION only in superuser-owned
functions. It would still be potentially useful that way. Doing this the
"right" way (with users needing regrantable privileges, etc.) would involve
too much effort for too little reward, IMHO.
(Repost - I don't think this made it to the list)
Bruce Momjian wrote:
> I am backing out this SET AUTHORIZATION patch until we can resolve the
> security issues. It will remain in the patch queue at:
In response to
pgsql-patches by date
|Next:||From: Anders Bengtsson||Date: 2001-07-13 13:59:13|
|Subject: Re: [PATCH] Cleanup of JDBC character encoding|
|Previous:||From: Bruce Momjian||Date: 2001-07-13 02:22:53|
|Subject: Re: Patch for handling long null terminated strings in JDBC driver|