Date: Mon, 9 May 2005 15:09:51 -0400 (EDT)
From: James Morris <jmorris@redhat.com>
To: Kristian =?iso-8859-1?q?S=F8rensen?= <ks@cs.aau.dk>
cc: Chris Friesen <cfriesen@nortel.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Any work in implementing Secure IPC for Linux?
In-Reply-To: <200505092044.29440.ks@cs.aau.dk>
Message-ID: <Xine.LNX.4.44.0505091508060.6382-100000@thoron.boston.redhat.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1225
Lines: 34

On Mon, 9 May 2005, Kristian S?rensen wrote:

> On Monday 09 May 2005 19:54, Chris Friesen wrote:
> > Kristian S?rensen wrote:
> > >  By "secure IPC" is meaning a
> > > security mechanism that provides a more fine granularity of specifying
> > > who are allowed to send (or receive) messages... and maby also a way to
> > > resolve the question of "Can I trust the message I received?"
> >
> > How about unix sockets?
> > 	--you can have sockets in the filesystem namespace with regular file
> > permissions to control who is allowed to send messages to particular
> > addresses
> This is the same problem: Basing access control on user and group is not 
> enough - especially as the root-user can overrule any access control 
> specified by the normal DAC file attributes.

You want MAC, in other words.

SELinux probably does what you want with fine grained MAC for Unix domain
networking and SO_PEERSEC for peer authentication.


- James
-- 
James Morris
<jmorris@redhat.com>


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/