From: "Kristian Sørensen" <ks@cs.aau.dk>
To: Chris Friesen <cfriesen@nortel.com>
Cc: James Morris <jmorris@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Any work in implementing Secure IPC for Linux?
Date: Mon, 9 May 2005 20:44:29 +0200 [thread overview]
Message-ID: <200505092044.29440.ks@cs.aau.dk> (raw)
In-Reply-To: <427FA3D4.1080706@nortel.com>
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 can authenticate who is sending the message using SCM_CREDENTIALS
I guess this poses the same problem as above?
KS
--
Kristian Sørensen
The Umbrella Project -- Security for Consumer Electronics
Linnovative -- www.linnovative.dk
ks@linnovative.dk -- +45 2972 3816
next prev parent reply other threads:[~2005-05-09 18:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 9:11 Kristian Sørensen
2005-05-09 12:15 ` Matthias-Christian Ott
2005-05-09 15:00 ` James Morris
2005-05-09 17:40 ` Kristian Sørensen
2005-05-09 17:53 ` Chris Wright
2005-05-09 17:54 ` Chris Friesen
2005-05-09 18:44 ` Kristian Sørensen [this message]
2005-05-09 19:01 ` Chris Wright
2005-05-09 19:09 ` James Morris
2005-05-09 18:06 ` Matthias-Christian Ott
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=200505092044.29440.ks@cs.aau.dk \
--to=ks@cs.aau.dk \
--cc=cfriesen@nortel.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome