All of lore.kernel.org
 help / color / mirror / Atom feed
From: "cto@itechfrontiers.com" <cto@itechfrontiers.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Joshua Brindle <method@manicmethod.com>,
	KaiGai Kohei <kaigai@ak.jp.nec.com>,
	selinux@tycho.nsa.gov
Subject: Re: Recent status of SE-PostgreSQL
Date: Thu, 09 Dec 2010 13:17:46 -0500	[thread overview]
Message-ID: <4D011D4A.6020504@itechfrontiers.com> (raw)
In-Reply-To: <4D01162F.5040107@schaufler-ca.com>

Casey,

The problem is you just stuck to one part of the argument and do not see 
the broad picture,

I never claimed anything ( here at least ), I just asked what is the 
practical purpose of SE-PostgreSQL and it had one line answer,

"creating trusted DBMS daemon",   and I see that

and of course nobody claims that the SE-PostgreSQL is a done project

so one has to wait until SE-PostgreSQL reaches the point,

I told it is possible to put databases on separate systems by 
classification, NOT SUCH a BIG DEAL, (while maintaining other forms of 
security measure including filesystem encryption and etc.)
THIS IS ACTUALLY BEING UTILIZED as I'm aware of

and there are Trusted Daemons nobody says there is  no trusted daemon,
The point is right now I think PostgreSQL is not qualified as a trusted 
daemon

but even right now you can use something like that in isolation, without 
combining classifications

SO THIS IS MY QUESTION NOW:
I would be very glad if anybody provides any documentation that 
PostgreSQL is currently treated as trusted daemon,

and thanks for your recommendation,

With all due respect to everybody especially KaiGai,

Let me clear that out, there is no objection of any kind on development 
of something, but what you claimed are not available at Postgres right 
now, and there are so many missing parts not just access control, and 
the point that it is being acceptable as trusted system is just a goal



Best Regards,


Patrick K.


On 12/9/2010 12:47 PM, Casey Schaufler wrote:
> On 12/9/2010 8:46 AM, cto@itechfrontiers.com wrote:
>> Joshua,
>>
>>> Postgres is inherently trusted with it's own objects, the kernel cannot  mitigate that.
>>
>> Aha that's the point, daemons cannot be trusted, in case of DBMS it must be isolated anyway, (System Security wise)
>
> I think that we can stop right here. Patrick, you need to go read up
> on the composition of trusted systems. You also need to put a little
> time into learning about their history. There were almost as many
> Orange Book evaluations on multi-level secure databases as there were
> on operating systems. All of the evaluated operating systems, with
> the possible exception of SC/MP, made heavy use of trusted daemons.
> Applications that enforce system policy are an expected and important
> part of any security solution.
>
> Patrick, the evidence is against your claims. Please have a look at
> the literature and come back if you have questions.
>
> Thank you.
>
>
>
>
> --
> This message was distributed to subscribers of the selinux mailing list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
> the words "unsubscribe selinux" without quotes as the message.


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

  reply	other threads:[~2010-12-09 18:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08  4:11 Recent status of SE-PostgreSQL KaiGai Kohei
2010-12-08 15:29 ` Ted Toth
2010-12-08 23:41   ` KaiGai Kohei
2010-12-09  0:33     ` cto
2010-12-09  8:36       ` KaiGai Kohei
2010-12-09 12:28         ` cto
2010-12-09 16:10           ` Joshua Brindle
2010-12-09 16:46             ` cto
2010-12-09 17:47               ` Casey Schaufler
2010-12-09 18:17                 ` cto [this message]
2010-12-09 20:07                   ` Joshua Brindle
2010-12-09 21:35                     ` cto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D011D4A.6020504@itechfrontiers.com \
    --to=cto@itechfrontiers.com \
    --cc=casey@schaufler-ca.com \
    --cc=kaigai@ak.jp.nec.com \
    --cc=method@manicmethod.com \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.