From: Stephen Hemminger <stephen@networkplumber.org>
To: Richard Haines <richard_c_haines@btinternet.com>
Cc: netdev@vger.kernel.org, selinux@tycho.nsa.gov
Subject: Re: [PATCH V3] ss: Add support for retrieving SELinux contexts
Date: Mon, 10 Mar 2014 13:24:04 -0700 [thread overview]
Message-ID: <20140310132404.6d792d30@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1394188612-3662-1-git-send-email-richard_c_haines@btinternet.com>
On Fri, 7 Mar 2014 10:36:52 +0000
Richard Haines <richard_c_haines@btinternet.com> wrote:
> The process SELinux contexts can be added to the output using the -Z
> option. Using the -z option will show the process and socket contexts (see
> the man page for details).
> For netlink sockets: if valid process show process context, if pid = 0
> show kernel initial context, if unknown show "unavailable".
>
> Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
Applied, thanks
prev parent reply other threads:[~2014-03-10 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 10:36 [PATCH V3] ss: Add support for retrieving SELinux contexts Richard Haines
2014-03-07 10:36 ` Richard Haines
2014-03-10 20:24 ` Stephen Hemminger [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=20140310132404.6d792d30@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=richard_c_haines@btinternet.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.