Re: SE-PgSQL patch review - Mailing list pgsql-hackers

From KaiGai Kohei
Subject Re: SE-PgSQL patch review
Date
Msg-id 4B15C854.6040305@ak.jp.nec.com
Whole thread Raw
In response to Re: SE-PgSQL patch review  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Josh Berkus wrote:
>> This is totally separate from the really important question of whether
>> SE-Linux has a future, and another about whether, if SE-Linux has a
>> future, PostgreSQL needs to go there.
> 
> If the hooks are generic enough that the could potentially be adapted to
> other security frameworks, yes.  The need to have cohesive centralized
> systems permissions management hasn't gone away, whatever anyone thinks
> of the SE-linux implementation.

In history, most of MAC feature have a common origin that was a research
in US military, so they have similar comcepts (such as security label,
a centralized security policy, ...) commonly.

It was the reason why I proposed PGACE framework for generic MAC features
at the earlier suggestion in v8.4 development cycle.
(Note that it had gone to separate unnecessary complexity now.)
As long as user can select his option, basically, I think it is preferable
to support multiple security models, not only SELinux.

As Linux (and also X-window) allows to host multiple MAC feature on a set
of common hooks, it is not an incorrect approach.
(Note that DAC has different origin from MAC, so we shall need a great
efforts to integrate them. My trial in CF#2 shows this failure.)

> That's why I was hoping to have the TrustedSolaris folks working on
> this, but we've pretty much lost access to them.

We can understand the current circumstance at Sun...

Thank,
-- 
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai@ak.jp.nec.com>


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Block-level CRC checks
Next
From: KaiGai Kohei
Date:
Subject: Re: SE-PgSQL patch review