All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Jason Axelson <jaxelson@referentia.com>
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: Show SELinux packet type of packets
Date: Tue, 29 May 2012 16:11:40 -0400	[thread overview]
Message-ID: <2272243.EJSO74OdnR@sifl> (raw)
In-Reply-To: <CAC9ii1oKMKNq5PA1oGLQYSx==s6R4wQ+HEVPu4wb5k9BNAsJaw@mail.gmail.com>

On Thursday, May 24, 2012 04:24:25 PM Jason Axelson wrote:
> Hi,
> 
> Is there a way to show the SELinux packet types of all packets?
> Ideally tcpdump would have an SELinux specific option that would print
> out the SELinux context of each packet but that seems to be missing.
> Are there any workarounds?
> 
> Note: this is with SECMARK labeling (such as
> http://james-morris.livejournal.com/11010.html)

Since secmark labels do not exist in the packets themselves, they are not 
visible via tcpdump or any other packet sniffer.  To the best of my knowledge 
there isn't a tool which will allow you to view local secmark labels.

If you are using labeled IPsec you could use tcpdump to determine the ESP 
and/or AH SPI and then use that to lookup the SA's SELinux label.

If you are using NetLabel/CIPSO then the label is part of the IP header and is 
visible using tcpdump.  Modern versions of wireshark understands how to parse 
the CIPSO label and displays it a more human readable format.

-- 
paul moore
www.paul-moore.com


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

  reply	other threads:[~2012-05-29 20:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-25  2:24 Show SELinux packet type of packets Jason Axelson
2012-05-29 20:11 ` Paul Moore [this message]
2012-05-31 20:30   ` Jason Axelson
2012-05-31 20:42     ` 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=2272243.EJSO74OdnR@sifl \
    --to=paul@paul-moore.com \
    --cc=jaxelson@referentia.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.