All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: HarryCiao <harrytaurus2002@hotmail.com>
Cc: "Christopher J. PeBenito" <cpebenito@tresys.com>,
	paul.moore@hp.com, selinux-mailing-list <selinux@tycho.nsa.gov>,
	refpolicy-mailing-list <refpolicy@oss1.tresys.com>
Subject: Re: Separate type for AF_UNIX socket created by syslogd_t
Date: Thu, 24 Feb 2011 13:18:26 -0500	[thread overview]
Message-ID: <1298571506.31953.55.camel@moss-pluto> (raw)
In-Reply-To: <SNT139-w42F5BDB103916DC8160624ABDA0@phx.gbl>

On Thu, 2011-02-24 at 10:44 +0000, HarryCiao wrote:
> BTW, do we have a way to actually display the label for the
> unix_dgram_socket that bond to /dev/log?

I think the answer is no at present.
netstat -Z claims to report the socket context but is actually just
reading /proc/pid/attr/current of the owning process.

The owning application can get the context of the socket (inode) via
fgetxattr(), but I don't think a third party can presently obtain the
context information.

-- 
Stephen Smalley
National Security Agency


--
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.

WARNING: multiple messages have this Message-ID (diff)
From: sds@tycho.nsa.gov (Stephen Smalley)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Separate type for AF_UNIX socket created by syslogd_t
Date: Thu, 24 Feb 2011 13:18:26 -0500	[thread overview]
Message-ID: <1298571506.31953.55.camel@moss-pluto> (raw)
In-Reply-To: <SNT139-w42F5BDB103916DC8160624ABDA0@phx.gbl>

On Thu, 2011-02-24 at 10:44 +0000, HarryCiao wrote:
> BTW, do we have a way to actually display the label for the
> unix_dgram_socket that bond to /dev/log?

I think the answer is no at present.
netstat -Z claims to report the socket context but is actually just
reading /proc/pid/attr/current of the owning process.

The owning application can get the context of the socket (inode) via
fgetxattr(), but I don't think a third party can presently obtain the
context information.

-- 
Stephen Smalley
National Security Agency

  parent reply	other threads:[~2011-02-24 18:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 10:44 Separate type for AF_UNIX socket created by syslogd_t HarryCiao
2011-02-24 10:44 ` [refpolicy] " HarryCiao
2011-02-24 13:35 ` Stephen Smalley
2011-02-24 13:35   ` [refpolicy] " Stephen Smalley
2011-02-24 15:52   ` Christopher J. PeBenito
2011-02-24 15:52     ` [refpolicy] " Christopher J. PeBenito
2011-02-26  3:29     ` HarryCiao
2011-02-26  3:29       ` [refpolicy] " HarryCiao
2011-03-04 10:38     ` Further questions about configuring contexts differently for variant classes HarryCiao
2011-03-04 10:38       ` [refpolicy] " HarryCiao
2011-03-04 10:57       ` Russell Coker
2011-03-04 13:46       ` Christopher J. PeBenito
2011-03-04 13:46         ` [refpolicy] " Christopher J. PeBenito
2011-03-04 14:04       ` Stephen Smalley
2011-03-04 14:04         ` [refpolicy] " Stephen Smalley
2011-02-24 18:18 ` Stephen Smalley [this message]
2011-02-24 18:18   ` [refpolicy] Separate type for AF_UNIX socket created by syslogd_t 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=1298571506.31953.55.camel@moss-pluto \
    --to=sds@tycho.nsa.gov \
    --cc=cpebenito@tresys.com \
    --cc=harrytaurus2002@hotmail.com \
    --cc=paul.moore@hp.com \
    --cc=refpolicy@oss1.tresys.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.