AW: AW: [PATCH] Re: Setuid functions - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: AW: [PATCH] Re: Setuid functions
Date
Msg-id 11C1E6749A55D411A9670001FA687963368348@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
Responses Re: AW: AW: [PATCH] Re: Setuid functions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> > Anybody else want to object to this abbreviation idea ?
> 
> I thought we already agreed to change the names per Peter's suggestion.
> 
> I didn't like the original names whether abbreviated or not ...

Good. I have not seen that agreement, maybe it was implied.
I am not sure whether the feature does not actually present a security 
hole ? Two collaborating users can pass each other their privileges.
I think we might need to guard that feature with a special privilege that 
the function creator needs during creation( e.g. dba).

And why not use the existing "set session authorization ..." syntax?
Because it would remain after function exit? Because it needs dba to execute ? 

Don't misunderstand, I like the feature, but this probably has to be considered.

Andreas


pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: RH announcement is there
Next
From: Tom Lane
Date:
Subject: Re: AW: AW: [PATCH] Re: Setuid functions