From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: Solar Designer <solar@openwall.com>
Cc: kernel-hardening@lists.openwall.com, oss-security@lists.openwall.com
Subject: Re: [kernel-hardening] Re: Security vulnerability tools
Date: Wed, 27 Mar 2013 17:17:08 -0400 [thread overview]
Message-ID: <515361D4.4040806@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130327201251.GA6480@openwall.com>
On 03/27/2013 04:12 PM, Solar Designer wrote:
> Hi,
>
> 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.
> On Wed, Mar 27, 2013 at 03:54:04PM -0400, Corey Bryant wrote:
>> I'll plan on updating http://oss-security.openwall.org/wiki/tools with
>> anything it doesn't already have.
>
> Yes, please!
>
>> Clang
>> -----
>> Static analysis tool for C/C++
>
> Clang and very recent GCC also have dynamic "sanitizers":
>
> http://clang.llvm.org/docs/AddressSanitizer.html
> http://clang.llvm.org/docs/ThreadSanitizer.html
> http://clang.llvm.org/docs/MemorySanitizer.html
Great, thanks!
>
> Thanks,
>
> Alexander
>
>
--
Regards,
Corey Bryant
next prev parent reply other threads:[~2013-03-27 21:17 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 [this message]
2013-03-28 7:32 ` Solar Designer
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=515361D4.4040806@linux.vnet.ibm.com \
--to=coreyb@linux.vnet.ibm.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=oss-security@lists.openwall.com \
--cc=solar@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).