All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: James Morris <jmorris@redhat.com>,
	SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: appletalk sockets
Date: Wed, 03 May 2006 14:25:36 -0400	[thread overview]
Message-ID: <1146680736.16160.4.camel@sgc> (raw)
In-Reply-To: <1146676995.20331.113.camel@sgc>

On Wed, 2006-05-03 at 13:23 -0400, Christopher J. PeBenito wrote:
> On Tue, 02 May 2006 at 13:57 -0400, Christopher J. PeBenito wrote:
> > On Tue, 2006-05-02 at 13:30 -0400, Daniel J Walsh wrote:
> > > Christopher J. PeBenito wrote:
> > > > On Tue, 2006-05-02 at 10:08 -0400, Daniel J Walsh wrote:
> > > >> cups needs to be able to create socket to itself.
> > > >
> > > > This needs more investigation; we need to find out more about this
> > > > generic socket so we can add a specific class for it.
> > > >
> > > >   
> > >
> > http://www.redhat.com/archives/fedora-selinux-list/2006-April/msg00216.html
> > 
> > So it appears that a class for appletalk sockets needs to be added.
> 
> How about the attached patches?

Perhaps permissions should be added to netif for appletalk send/receive
too, so it doesn't fall through to rawip send/receive?

-- 
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150


--
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:[~2006-05-03 18:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 17:23 appletalk sockets Christopher J. PeBenito
2006-05-03 18:25 ` Christopher J. PeBenito [this message]
2006-05-03 18:39   ` Stephen Smalley

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=1146680736.16160.4.camel@sgc \
    --to=cpebenito@tresys.com \
    --cc=jmorris@redhat.com \
    --cc=sds@epoch.ncsc.mil \
    --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.