From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Dominick Grift <dominick.grift@gmail.com>,
Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov
Subject: Re: Showing port Labels
Date: Mon, 14 Jul 2014 10:50:48 -0400 [thread overview]
Message-ID: <53C3EE48.6050704@tresys.com> (raw)
In-Reply-To: <1405344305.661.33.camel@x220.localdomain>
On 7/14/2014 9:25 AM, Dominick Grift wrote:
> On Mon, 2014-07-14 at 08:58 -0400, Stephen Smalley wrote:
> < snip >
>
>>> It is probably not the answer you were looking for but i suppose I would
>>> use seinfo --portcon
>>
>> sepolicy network -p <portnumber>
>>
>>
>
> Yes, but i prefer minimal/small (and preferably no interpreters):
>
> # file /usr/bin/seinfo
> /usr/bin/seinfo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
> dynamically linked (uses shared libs), for GNU/Linux 2.6.32,
> BuildID[sha1]=04ae4e364753b502f227216e548e1ccbf0f33e14, stripped
>
> # file /usr/bin/sepolicy
> /usr/bin/sepolicy: Python script, ASCII text executable, with very long
> lines
sepolicy is using libapol from setools, so its not really different than
seinfo, other than using a Python frontend. Since SETools 4 is Python,
you'll eventually be running low on choices if you're trying to stick to
only C tools :)
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2014-07-14 14:50 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 [this message]
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
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=53C3EE48.6050704@tresys.com \
--to=cpebenito@tresys.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.