From: "Justin P. Mattock" <justinmattock@gmail.com>
To: KaiGai Kohei <kaigai@ak.jp.nec.com>
Cc: russell@coker.com.au, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: netstat -Z
Date: Mon, 19 Jan 2009 01:35:09 -0800 [thread overview]
Message-ID: <4974494D.8040104@gmail.com> (raw)
In-Reply-To: <497434CA.1070104@ak.jp.nec.com>
KaiGai Kohei wrote:
> Russell Coker wrote:
>> The command "netstat -Z -t" will show two entries for a localhost
>> connection and thus show the context of each end of the socket.
>>
>> The command "netstat -Z -x" seems to only show a single entry for the
>> connection which will be from the server end.
>>
>> http://wiki.postgresql.org/wiki/SEPostgreSQL
>>
>> The above wiki page mentions "netstat -Z" and my personal
>> interpretation of this was that I could use "netstat -Z" to find the
>> context of a client end of a socket. But it seems that I can only
>> get the server end.
>>
>> Is this what is desired?
>
> Please note that the above wiki entry is on "postgresql.org".
> It assumes PostgreSQL folds (not SELinux specialist) as audiences.
> The purpose of description about "netstat -Z" is to make clear
> the fact security context can be assigned to various kind of
> objects (like socket), except for filesystem also.
>
> Thanks,
Well; it's nice issuing:
ps auxZ to achieve some stats,
as opposed to ps au*;
In any case -Z would be nice to see,
regards;
Justin P. Mattock
--
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.
next prev parent reply other threads:[~2009-01-19 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 8:32 netstat -Z Russell Coker
2009-01-19 8:07 ` KaiGai Kohei
2009-01-19 9:35 ` Justin P. Mattock [this message]
2009-01-19 8:17 ` Justin P. Mattock
2009-01-20 17:32 ` Paul Moore
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=4974494D.8040104@gmail.com \
--to=justinmattock@gmail.com \
--cc=kaigai@ak.jp.nec.com \
--cc=russell@coker.com.au \
--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.