From: Chuck Ebbert <76306.1226@compuserve.com>
To: Ahmed Masud <masud@googgun.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: SNARE and C2 auditing under 2.5.x
Date: Wed, 21 May 2003 06:40:47 -0400 [thread overview]
Message-ID: <200305210642_MC3-1-39D2-5928@compuserve.com> (raw)
> I may be repeating this question, but is there an effort to brigning
> snare code to 2.5.x?
Nah, auditing isn't needed to run a secure system. ;)
next reply other threads:[~2003-05-21 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 10:40 Chuck Ebbert [this message]
2003-05-21 19:26 ` Bernd Eckenfels
2003-05-21 22:56 ` Alan Cox
2003-05-23 11:55 ` Jakob Oestergaard
-- strict thread matches above, loose matches on Subject: below --
2003-06-10 11:57 Red Phoenix
2003-05-17 11:31 Ahmed Masud
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=200305210642_MC3-1-39D2-5928@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masud@googgun.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome