Skip site navigation (1) Skip section navigation (2)

AW: [PATCH] Re: Setuid functions

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, Mark Volpe <volpe(dot)mark(at)epa(dot)gov>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: AW: [PATCH] Re: Setuid functions
Date: 2001-06-25 10:12:42
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> > This patch will implement the "ENABLE PRIVILEGE" and "DISABLE PRIVILEGE"
> > commands   in PL/pgSQL, which, respectively, change the effective uid to that
> > of the function owner and back. It doesn't break security (I hope). The
> > commands can be abbreviated as "ENABLE" and "DISABLE" for the poor saps that

Anybody else want to object to this abbreviation idea ? Seems 
reading ENABLE; or DISABLE; is very hard to interpret in source code
(enable what ?) and should thus not be allowed (or allow "ENABLE PRIV").



pgsql-hackers by date

Next:From: Zeugswetter Andreas SBDate: 2001-06-25 10:17:10
Subject: AW: Good name for new lock type for VACUUM?
Previous:From: Lincoln YeohDate: 2001-06-25 06:34:51
Subject: Re: Encrypting pg_shadow passwords

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group