All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Quigley <selinux@davequigley.com>
To: Stephen Smalley <sds@tycho.nsa.gov>,
	Dominick Grift <dominick.grift@gmail.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: Showing port Labels
Date: Mon, 14 Jul 2014 12:52:15 -0400	[thread overview]
Message-ID: <53C40ABF.20408@davequigley.com> (raw)
In-Reply-To: <53C3D401.6030207@tycho.nsa.gov>

On 7/14/2014 8:58 AM, Stephen Smalley wrote:
> On 07/14/2014 05:25 AM, Dominick Grift wrote:
>> On Mon, 2014-07-14 at 02:49 -0400, Dave Quigley wrote:
>>> I am working on some slides for my workshop at oscon and I tried to find
>>> the context of a port a process is listening on. If I do netstat -lZ I
>>> see all the listening ports and a security context. However, it seems
>>> the security context is the context of the process that is listening on
>>> that port not the context of the port itself. Is there a way to see the
>>> context of the port itself? I don't see any other option that might give
>>> that information. Is there a way to get that information from proc? Or
>>> are the only components that know the context of a port the kernel and
>>> the policy store?
>>
>> It is probably not the answer you were looking for but i suppose I would
>> use seinfo --portcon
>
> sepolicy network -p <portnumber>
>
>

Also is there ideological reason why we don't support portcon or 
semanage port statements to override a port definition in the base module?

Dave

      parent reply	other threads:[~2014-07-14 16:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14  6:49 Showing port Labels Dave Quigley
2014-07-14  9:25 ` Dominick Grift
2014-07-14 12:58   ` Stephen Smalley
2014-07-14 13:25     ` Dominick Grift
2014-07-14 14:50       ` Christopher J. PeBenito
2014-07-14 15:10         ` Dominick Grift
2014-07-14 16:50     ` Dave Quigley
2014-07-14 16:51       ` Stephen Smalley
2014-07-14 16:52     ` Dave Quigley [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=53C40ABF.20408@davequigley.com \
    --to=selinux@davequigley.com \
    --cc=dominick.grift@gmail.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.