All of lore.kernel.org
 help / color / mirror / Atom feed
From: ole@plastictree.net
To: Frank C <frankc@networkcrypt.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: Strange context on unix_stream_socket
Date: Sun, 26 Jan 2014 13:33:31 +0100	[thread overview]
Message-ID: <20140126123331.GB2837@telmora.telvanni> (raw)
In-Reply-To: <CAPJdAQCZ0W4Bbm5JGa+R4QQkkeddoZFdUn5icJyo07xAB7BvNw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3004 bytes --]

On Sun, Jan 26, 2014 at 06:01:51AM +0800, Frank C wrote:
> So does this mean that we have sockets that are left open for discussion
> that are not being used?  They all have to come out if they are not being
> used.  Unused sockets shouldn't pass a static analysis.

Thank you for your input. Unfortunately I cannot quite follow. 
Could you please elaborate what your question is?

My problem is that a socket created by the accept system call 
(see my follow-up posting) has not only a wrong context that 
prevents access to it, but also a context that following the 
policy it should not be able to acquire.


> 
> 
> On Sun, Jan 26, 2014 at 4:59 AM, Ole Kliemann <ole@plastictree.net> wrote:
> 
> > I'm having an odd problem:
> >
> > I am running my own MCS constrainted policy on Ubuntu 12.04. At
> > some point I have a process with context
> >
> >     sub_t:s0:c20-s0:c20.c29
> >
> > From this process I try to access a jack daemon with mplayer. For
> > this purpose unix stream sockets are being used. I then get an
> > avc denial saying that
> >
> >     process sub_t:s0:c20-s0:c20.c29
> >
> > tried to access
> >
> >     unix_stream_socket sub_t:s0
> >
> > which is prohibited by mcs constrain. The socket is on sockfs and
> > has no file associated with it.
> >
> > The problem is that under no circumstances the policy allows the
> > creation of anything with 'sub_t:s0'.
> >
> > Using an auditallow rule like
> >
> >     auditallow any_type sub_t:unix_stream_socket { create relabelto
> > relabelfrom };
> >
> > clearly shows that indeed no socket with a context like that is
> > created nor relabel to.  And yet it exists.
> >
> >
> > I'd highly appreciate any hint on this matter. Including how to
> > debug further. How can I display the security context of a socket
> > on sockfs?
> >
> > Best regards
> > Ole
> >
> > _______________________________________________
> > Selinux mailing list
> > Selinux@tycho.nsa.gov
> > To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
> > To get help, send an email containing "help" to
> > Selinux-request@tycho.nsa.gov.
> >
> >
> 
> 
> -- 
> 
> *Francis X. Cunnane III*
> frankc@networkcrypt.com
> 
> 
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. If you are not the intended recipient
> you are notified that disclosing, copying, distributing or taking any
> action in reliance on the contents of this information is strictly
> prohibited.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      parent reply	other threads:[~2014-01-26 12:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-25 20:59 Strange context on unix_stream_socket Ole Kliemann
2014-01-26 12:29 ` Ole Kliemann
2014-01-26 22:46   ` Ole Kliemann
2014-01-27 16:20     ` Stephen Smalley
2014-01-28 17:12       ` Ole Kliemann
2014-01-28 17:22         ` Stephen Smalley
2014-01-30 15:10           ` Richard Haines
2014-01-30 15:15             ` Stephen Smalley
2014-01-30 18:33             ` Ole Kliemann
     [not found] ` <CAPJdAQCZ0W4Bbm5JGa+R4QQkkeddoZFdUn5icJyo07xAB7BvNw@mail.gmail.com>
2014-01-26 12:33   ` ole [this message]

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=20140126123331.GB2837@telmora.telvanni \
    --to=ole@plastictree.net \
    --cc=frankc@networkcrypt.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.