From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: New init system hitting a distro near you.
Date: Fri, 18 Jun 2010 16:00:50 -0400 [thread overview]
Message-ID: <4C1BD072.10700@redhat.com> (raw)
In-Reply-To: <1276890327.22449.135.camel@moss-pluto.epoch.ncsc.mil>
On 06/18/2010 03:45 PM, Stephen Smalley wrote:
> On Fri, 2010-06-18 at 15:34 -0400, Daniel J Walsh wrote:
>> http://0pointer.de/blog/projects/systemd.html
>>
>> This has interesting ramifications for SELinux. I have a working
>> version of this in Fedora 14, but we need to add rules like
>>
>> allow sshd_t init_t:tcp_socket { getopt ioctl getattr setopt };
>>
>> Since systemd will be doing the listening and passing the socket to sshd.
>>
>> Could we have risks of sshd_t grabbing the tcp_socket connected to
>> httpd_t?
>>
>> In this scenario we are no longer protecting against the name_bind, and
>> are forced to put more trust into init_t.
>
> Can we get systemd to use setsockcreatecon() to assign the right label
> to the socket?
>
Probably but how does it figure out the context?
--
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.
next prev parent reply other threads:[~2010-06-18 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 19:34 New init system hitting a distro near you Daniel J Walsh
2010-06-18 19:44 ` Daniel J Walsh
2010-06-18 19:45 ` Stephen Smalley
2010-06-18 20:00 ` Daniel J Walsh [this message]
2010-06-18 20:22 ` Stephen Smalley
2010-06-18 20:29 ` Daniel J Walsh
2010-06-18 20:31 ` Stephen Smalley
2010-06-21 15:20 ` Paul Moore
2010-06-21 15:26 ` Stephen Smalley
2010-06-21 17:35 ` Paul Moore
2010-07-19 19:42 ` Daniel J Walsh
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=4C1BD072.10700@redhat.com \
--to=dwalsh@redhat.com \
--cc=sds@tycho.nsa.gov \
--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.