From: Nero <neroz@iinet.net.au>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [CHECKER] 18 potential security holes
Date: Tue, 12 Nov 2002 21:35:46 +1100 [thread overview]
Message-ID: <3DD0D982.6070209@iinet.net.au> (raw)
In-Reply-To: <Pine.GSO.4.21.0211121723560.3966-100000@steklov.math.psu.edu>
Alexander Viro wrote:
>
> On Tue, 12 Nov 2002, Nero wrote:
>
>
> >>great to see stanford running this again! it has been extremely helpful
> >>in the past
> >>
> >>thanks!
> >>
> >>j.
> >
> >
> >Why isn't the code for this available?
>
>
> Presumably because its authors do not want it to be available. Their
> right - they publish results of running their code, but do not distribute
> the code itself, so for all practical purposes it falls under "you are
> not forced to distribute the local modifications you've made". RTFGPL...
I didn't say they should have to.
prev parent reply other threads:[~2002-11-12 22:29 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
2002-11-12 10:13 ` Nero
2002-11-12 22:28 ` Alexander Viro
2002-11-12 10:35 ` Nero [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=3DD0D982.6070209@iinet.net.au \
--to=neroz@iinet.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.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