Re: [PATCH] SE-PostgreSQL Security Policy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2008-03-07 at 10:52 +0900, Kohei KaiGai wrote:
> Christopher J. PeBenito wrote:
> > On Wed, 2008-02-27 at 17:00 +0900, Kohei KaiGai wrote:
> >> The attached patch provides security policies related to
> >> SE-PostgreSQL.
[...]
> >> +typeattribute unlabeled_t      sepgsql_database_type;
> >> +typeattribute unlabeled_t      sepgsql_table_type;
> >> +typeattribute unlabeled_t      sepgsql_procedure_type;
> >> +typeattribute unlabeled_t      sepgsql_blob_type;
> > 
> > Usage of unlabeled_t here is not permitted.
> 
> Is it appropriate manner to deploy optional_policy at kernel/kernel.te?

Why is this needed at all?

> >> +########################################
> >> +#
> >> +# SE-PostgreSQL Administrative domain local policy
> >> +#                    (sepgsql_unconfined_type)
> >> +
> >> +tunable_policy(`sepgsql_enable_unconfined',`
> >> +       allow sepgsql_unconfined_type sepgsql_database_type : db_database *;
> >> +       allow sepgsql_unconfined_type sepgsql_module_type : db_database { install_module };
> >> +       allow sepgsql_unconfined_type sepgsql_table_type : { db_table db_column db_tuple } *;
> >> +       allow sepgsql_unconfined_type { sepgsql_procedure_type - sepgsql_user_proc_t } : db_procedure *;
> >> +       allow sepgsql_unconfined_type sepgsql_user_proc_t : db_procedure { create drop getattr setattr relabelfrom relabelto };
> >> +       allow sepgsql_unconfined_type sepgsql_blob_type : db_blob *;
> >> +       allow sepgsql_unconfined_type postgresql_t : db_blob { import export };
> >> +
> >> +       type_transition { sepgsql_unconfined_type - sepgsql_server_type } sepgsql_database_type : db_procedure sepgsql_proc_t;
> >> +',`
> >> +       type_transition { sepgsql_unconfined_type - sepgsql_server_type } sepgsql_database_type : db_procedure sepgsql_user_proc_t;
> >> +')
> > 
> > Why is this tunable?  Why is there a different type_transition behavior?
> 
> I intend that users can turn off this tunable during its operation phase
> after initial database setting up, to prevent applying unconfined accesses.
> 
> When sepgsql_enable_unconfined is disabled, sepgsql_unconfined_type works
> as if they are sepgsql_client_type, because sepgsql_unconfined_domain() interface
> associates a domain with sepgsql_(unconfined|client)_type.

The problem is that this is inconsistent with the way other
*_unconfined() access works.

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



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.

[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux