From: Russ Allbery <rra@stanford.edu>
To: oss-security@lists.openwall.com
Cc: kernel-hardening@lists.openwall.com
Subject: [kernel-hardening] Re: [oss-security] Security vulnerability tools
Date: Wed, 27 Mar 2013 13:31:35 -0700 [thread overview]
Message-ID: <877gkswpnc.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <51534E5C.8070303@linux.vnet.ibm.com> (Corey Bryant's message of "Wed, 27 Mar 2013 15:54:04 -0400")
Corey Bryant <coreyb@linux.vnet.ibm.com> writes:
> Clang
> -----
> Static analysis tool for C/C++
Clang is, properly speaking, a compiler. It happens to also have a static
analyzer available as part of the same code base.
If you're going to mention Clang, it's probably also pointing out that
good old GCC has very extensive warning flags that can, among other
things, find possible security vulnerabilities by locating variables that
are used before being set, dangerous printf formats, mismatches between
printf formats and arguments, and so forth. For example, I currently use:
WARNINGS = -g -O -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wendif-labels \
-Wformat=2 -Winit-self -Wswitch-enum -Wdeclaration-after-statement \
-Wshadow -Wpointer-arith -Wbad-function-cast -Wcast-align \
-Wwrite-strings -Wjump-misses-init -Wlogical-op \
-Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls \
-Wnested-externs -Werror
with GCC (4.6 or later) with all of my software. Many of those are not
security-related, of course, but -Wformat=2 certainly is, and some of the
-Wall and -Wextra warnings are as well.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
prev parent reply other threads:[~2013-03-27 20:31 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
2013-04-08 5:37 ` Hasinoliva MIARIMANJATO
2013-03-27 20:31 ` Russ Allbery [this message]
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=877gkswpnc.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
--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 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.