All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joshua Brindle" <JBrindle@snu.edu>
To: <SELinux@tycho.nsa.gov>, <wlsel@verizon.net>
Subject: Re: SELinux, KDE, and honeypots
Date: Wed, 09 Jul 2003 09:30:37 -0500	[thread overview]
Message-ID: <sf0be0df.042@atlas.snu.edu> (raw)

>The idea I had was to create a pseudo-device driver that leverages
NetFilter 
>to output all traffic from all TCP streams to a user-mode daemon that
writes 
>the packets for each stream into their own separate disk files (and
governing 
>the throughput if need be so that the transcribing daemon can keep up
with 
>the traffic).  If no security violations are reported during the
lifetime of 
>the TCP stream, then when it is closed the transcript is moved to a
directory 
>where it remains for some period of time (perhaps for auditing
purposes) 
>before being routinely deleted.

this is sorta offtopic so i'll just quickly say it would be insane to
try and
handle that with netfilter.. you can use libpcap but that would take
decades to review, your best bet is to plug in an IDS like prelude
(www.prelude-ids.org) to monitor tcp traffic for violations. we are
looking
into getting rules written for the prelude log monitor to understand
selinux avc messages so thats a plus (prelude is hybrid ids, that is
net + host ids) so you can monitor network traffic on your router
and host ids (logs, file digests, etc) on your other machines.

--
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:[~2003-07-09 14:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 14:30 Joshua Brindle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-09  3:03 SELinux, KDE, and honeypots Bill Laut
2003-07-09  8:20 ` Tom
2003-07-09  9:48   ` Russell Coker
2003-07-09  9:26 ` Russell Coker
2003-07-09 18:08   ` Bill Laut
2003-07-10  2:20     ` Russell Coker
2003-07-10  8:09       ` Bill Laut
2003-07-09 22:41 ` Tracy R Reed
2003-07-10  7:25   ` Bill Laut

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=sf0be0df.042@atlas.snu.edu \
    --to=jbrindle@snu.edu \
    --cc=SELinux@tycho.nsa.gov \
    --cc=wlsel@verizon.net \
    /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.