From: Hank Leininger <linux-kernel@progressive-comp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [CHECKER] security rules? (and 2.4.5-ac4 security bug)
Date: Mon, 4 Jun 2001 08:20:01 -0400 [thread overview]
Message-ID: <200106041220.IAA07493@mailer.progressive-comp.com> (raw)
On 2001-06-03, Dawson Engler <engler@csl.Stanford.EDU> wrote:
> Additionally, do people have suggestions for good security rules?
> We're looking to expand our security checkers. Right now we just have
> checkers that warn when:
Do you already have checks for signed/unsigned issues? Those often result
in security problems, although you may already be checking for them simply
for reliable-code purposes. ...Hm, looking at the archives, I see Chris
Evans responded about signedness issues when you asked last month :-P
You may want to check out and/or subscribe to the security-audit list; most
of the discussion is about userland security issues but kernel problems (or
potential ones) are discussed as well. We have archives of the list at:
http://marc.theaimsgroup.com/?l=linux-security-audit&r=1&w=2
And see http://www.linuxhelp.org/lsap.shtml for more info, subscribing,
etc.
--
Hank Leininger <hlein@progressive-comp.com>
next reply other threads:[~2001-06-04 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 12:20 Hank Leininger [this message]
2001-06-09 18:07 ` [CHECKER] security rules? (and 2.4.5-ac4 security bug) Theodore Tso
2001-06-10 2:13 ` Dawson Engler
-- strict thread matches above, loose matches on Subject: below --
2001-06-03 8:07 Dawson Engler
2001-06-03 11:22 ` Alan Cox
2001-06-08 11:24 ` Florian Weimer
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=200106041220.IAA07493@mailer.progressive-comp.com \
--to=linux-kernel@progressive-comp.com \
--cc=hlein@progressive-comp.com \
--cc=linux-kernel@vger.kernel.org \
/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