From: john slee <indigoid@higherplane.net>
To: Russell Greene <rdg12@stanford.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [CHECKER] 18 potential security holes
Date: Tue, 12 Nov 2002 18:26:07 +1100 [thread overview]
Message-ID: <20021112072607.GC17478@higherplane.net> (raw)
In-Reply-To: <5.1.0.14.2.20021111143426.045c4d90@rdg12.pobox.stanford.edu>
On Mon, Nov 11, 2002 at 02:35:06PM -0800, Russell Greene wrote:
> You can look at this checker as essentially tracking whether the
> information from an untrusted source (e.g., from copy_from_user) can reach
> a trusting sink (e.g., an array index).
great to see stanford running this again! it has been extremely helpful
in the past
thanks!
j.
--
toyota power: http://indigoid.net/
next prev parent reply other threads:[~2002-11-12 7:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 22:35 [CHECKER] 18 potential security holes Russell Greene
2002-11-12 7:26 ` john slee [this message]
2002-11-12 10:13 ` Nero
2002-11-12 22:28 ` Alexander Viro
2002-11-12 10:35 ` Nero
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=20021112072607.GC17478@higherplane.net \
--to=indigoid@higherplane.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rdg12@stanford.edu \
/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