From: Solar Designer <solar@openwall.com>
To: Corey Bryant <coreyb@linux.vnet.ibm.com>
Cc: kernel-hardening@lists.openwall.com, oss-security@lists.openwall.com
Subject: [kernel-hardening] Re: Security vulnerability tools
Date: Thu, 28 Mar 2013 11:32:16 +0400 [thread overview]
Message-ID: <20130328073216.GA6962@openwall.com> (raw)
In-Reply-To: <515361D4.4040806@linux.vnet.ibm.com>
On Wed, Mar 27, 2013 at 05:17:08PM -0400, Corey Bryant wrote:
> On 03/27/2013 04:12 PM, Solar Designer wrote:
> >Guys, can we continue this thread on oss-security only, please? It is a
> >topic for oss-security, but less so for kernel-hardening. Anyone on
> >kernel-hardening who is interested in this topic should join oss-security.
> >
> >Just drop kernel-hardening from further replies.
>
> Sure, sorry about that. I am interested in tools that are applicable to
> the kernel too though, if that changes anything.
It makes sense for you to post a summary of the relevant ones of your
updates to http://oss-security.openwall.org/wiki/tools to
kernel-hardening after this discussion thread on oss-security is mostly
over. Other than that, I think it's best to keep the thread on
oss-security only. Cross-posting all or almost all of it is a mess.
(Hopefully, this is the last cross-post I have to make in this thread.)
Thanks!
Alexander
next prev parent reply other threads:[~2013-03-28 7:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 19:54 [kernel-hardening] Security vulnerability tools Corey Bryant
2013-03-27 19:58 ` Tim Brown
2013-03-27 20:12 ` [kernel-hardening] " Solar Designer
2013-03-27 21:17 ` Corey Bryant
2013-03-28 7:32 ` Solar Designer [this message]
2013-04-08 5:37 ` Hasinoliva MIARIMANJATO
2013-03-27 20:31 ` [kernel-hardening] Re: [oss-security] " Russ Allbery
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=20130328073216.GA6962@openwall.com \
--to=solar@openwall.com \
--cc=coreyb@linux.vnet.ibm.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=oss-security@lists.openwall.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;
as well as URLs for NNTP newsgroup(s).