From: Jesse Stockall <stockall@magma.ca>
To: Mark Adler <madler@alumni.caltech.edu>
Cc: Paul Jackson <pj@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gcc 3.5 fixes
Date: Mon, 05 Jul 2004 23:51:08 -0400 [thread overview]
Message-ID: <1089085868.8452.2.camel@localhost> (raw)
In-Reply-To: <1C37F9C6-CEEA-11D8-B083-000A95820F30@alumni.caltech.edu>
On Mon, 2004-07-05 at 21:16, Mark Adler wrote:
>
> It's not about the copyright. I like the string kept in the object
> code so that I and others can find out where the code is used and what
> version is in use. This in fact turned out to be useful when a
> security vulnerability was found in versions 1.1.3 and earlier and a
> script could search for executables with the offending code.
>
<-- snip -->
> " inflate 1.1.3 Copyright 1995-1998 Mark Adler "
Did I miss something or are you saying that the version in the kernel
has a security vulnerability?
Jesse
--
Jesse Stockall <stockall@magma.ca>
next prev parent reply other threads:[~2004-07-06 3:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2e9is-5YT-1@gated-at.bofh.it>
[not found] ` <2e9iu-5YT-5@gated-at.bofh.it>
[not found] ` <2ecq2-80i-1@gated-at.bofh.it>
[not found] ` <7ab39013.0407042237.40ea9035@posting.google.com>
[not found] ` <20040705064010.C9BFB5F7AA@attila.bofh.it>
2004-07-05 16:51 ` [PATCH] gcc 3.5 fixes Mark Adler
2004-07-05 21:44 ` Paul Jackson
2004-07-06 1:16 ` Mark Adler
2004-07-06 1:45 ` Paul Jackson
2004-07-06 3:51 ` Jesse Stockall [this message]
2004-07-06 4:43 ` Mark Adler
2004-07-06 6:11 ` bert hubert
2004-07-06 6:46 ` David Woodhouse
2004-07-06 15:02 ` Mark Adler
2004-07-04 6:58 Anton Blanchard
2004-07-04 7:01 ` Anton Blanchard
2004-07-04 7:07 ` Anton Blanchard
2004-07-04 10:24 ` Bartlomiej Zolnierkiewicz
2004-07-04 11:04 ` Anton Blanchard
2004-07-06 15:28 ` Randy.Dunlap
2004-07-11 10:23 ` Anton Blanchard
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=1089085868.8452.2.camel@localhost \
--to=stockall@magma.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=madler@alumni.caltech.edu \
--cc=pj@sgi.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.