[refpolicy] [PATCH] Add a new permission to db_procedure

Christopher J. PeBenito cpebenito at tresys.com
Tue Jan 20 08:31:11 CST 2009


On Tue, 2009-01-20 at 17:19 +0900, KaiGai Kohei wrote:
> This is just an aside, I would like to make a rapid conclusion due to
> the current (v8.4) PostgreSQL development cycle, if possible.
> 
>   http://wiki.postgresql.org/wiki/CommitFestInProgress
> 
> KaiGai Kohei wrote:
> > The attached patch add a new permission named as "install" to db_procedure.
> > 
> > The purpose of this permission is to prevent malicious functions are invoked
> > as a part of server's internal tasks.
> > 
> > PostgreSQL allows user-defined functions to use its internal tasks.
> > For example, it can be used to implement an output/input handler of new data
> > types, an index access method, implementation of operator classes and so on.
> > 
> > When we defines a new type, it requires to specify its output/input handler
> > at least. No need to say, these functions should not be malicious ones,
> > because user implicitly invokes these function when he uses the type.
> > This permission is checked when we defines a new system catalog entry which
> > has a possibility to invoke user defined functions.
> > 
> > In the attached patch, only sepgsql_proc_t is allowed to { install }, because
> > any other user defined functions are not checked by DBA, so it is not safe to
> > use it as a part of internal/common processes.
> > If DBA want to apply user defined functions as a part of internal task, he has
> > to confirm its safeness and relabel to sepgsql_proc_t at first.
> > 
> > Please apply it, if no matter.

Changes to object classes need to be discussed on the SELinux list.

-- 
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150



More information about the refpolicy mailing list