From: mdew <mdew@mdew.dyndns.org>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: Christoph Pleger <Christoph.Pleger@uni-dortmund.de>,
lkml <linux-kernel@vger.kernel.org>,
linux-adm@vger.kernel.org
Subject: Re: Security Patches
Date: 03 Aug 2003 02:07:57 +1200 [thread overview]
Message-ID: <1059833276.16002.1.camel@mdew> (raw)
In-Reply-To: <200308011636.45470.m.c.p@wolk-project.de>
On Sat, 2003-08-02 at 02:36, Marc-Christian Petersen wrote:
> On Friday 01 August 2003 16:28, Christoph Pleger wrote:
>
> Hi Christoph,
>
> > In the last few days I read some security advisories about security
> > patches for Linux Kernels of the 2.4-series which have been published by
> > various distributors.
> > Does anybody know of a URL where such fixes for the stable Kernel 2.4.21
> > can be found? The best place would be a place where always actual kernel
> > security fixes can be found and where, if the patches are already
> > integrated into the kernel, it contains no other differences from the
> > stable release.
> please go to: http://linux.bkbits.net:8080/linux-2.4
talking of which, is http://linux.bkbits.net:8080/linux-2.5 dead? a week
with absolutely no changes?
--
mdew <mdew@mdew.dyndns.org>
next prev parent reply other threads:[~2003-08-02 14:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 14:28 Security Patches Christoph Pleger
2003-08-01 14:36 ` Marc-Christian Petersen
2003-08-02 14:07 ` mdew [this message]
2003-08-04 7:19 ` Christoph Pleger
-- strict thread matches above, loose matches on Subject: below --
2012-09-06 8:31 Security patches kk s
2012-09-06 8:56 ` Ian Campbell
2012-09-06 9:08 ` kk s
[not found] ` <CAPU-Ed4=r6KT0r4fM--94oPPo0mn4LcmwRJh41wHiAFvf6irLg@mail.gmail.com>
2012-09-06 9:13 ` Ian Campbell
2012-09-06 10:50 ` kk s
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=1059833276.16002.1.camel@mdew \
--to=mdew@mdew.dyndns.org \
--cc=Christoph.Pleger@uni-dortmund.de \
--cc=linux-adm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
/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.