From: "H. Peter Anvin" <hpa@zytor.com>
To: Valdis.Kletnieks@vt.edu
Cc: John Bradford <john@grabjohn.com>, linux-kernel@vger.kernel.org
Subject: Re: kernel.org frontpage
Date: Wed, 29 Jan 2003 10:13:31 -0800 [thread overview]
Message-ID: <3E3819CB.2090409@zytor.com> (raw)
In-Reply-To: 200301291509.h0TF9S4K003537@turing-police.cc.vt.edu
Valdis.Kletnieks@vt.edu wrote:
> On Wed, 29 Jan 2003 01:52:43 PST, "H. Peter Anvin" said:
>
>
>>No, it would add absolutely nothing (other than clutter.) All the .sign
>>files are good for is to check for rogue mirrors.
>
>
> Or a rogue *primary* site, as has already happened to OpenSSH and Sendmail.
NO!
THE SIGN FILES DO NOT VERIFY AGAINST A COMPROMISED KERNEL.ORG MASTER SITE.
-hpa
next prev parent reply other threads:[~2003-01-29 18:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 5:40 kernel.org frontpage H. Peter Anvin
2003-01-29 9:47 ` John Bradford
2003-01-29 9:52 ` H. Peter Anvin
2003-01-29 15:09 ` Valdis.Kletnieks
2003-01-29 18:13 ` H. Peter Anvin [this message]
2003-01-29 18:36 ` Chris Friesen
2003-01-29 18:55 ` Valdis.Kletnieks
2003-01-29 19:37 ` Russell King
2003-01-29 19:49 ` Valdis.Kletnieks
2003-01-29 19:14 ` John Bradford
2003-01-29 19:20 ` Valdis.Kletnieks
2003-01-29 19:30 ` H. Peter Anvin
2003-01-30 10:55 ` Hans Reiser
2003-01-29 19:54 ` John Bradford
2003-01-29 19:29 ` H. Peter Anvin
2003-01-29 19:58 ` John Bradford
2003-01-30 20:42 ` Kasper Dupont
2003-01-30 20:44 ` H. Peter Anvin
2003-01-30 20:50 ` John Bradford
[not found] <200301290947.h0T9lKa9000750@darkstar.example.net.suse.lists.linux.kernel>
[not found] ` <3E37A46B.4080907@zytor.com.suse.lists.linux.kernel>
[not found] ` <200301291509.h0TF9S4K003537@turing-police.cc.vt.edu.suse.lists.linux.kernel>
[not found] ` <3E3819CB.2090409@zytor.com.suse.lists.linux.kernel>
[not found] ` <3E381F47.8060200@nortelnetworks.com.suse.lists.linux.kernel>
2003-01-29 18:55 ` Andi Kleen
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=3E3819CB.2090409@zytor.com \
--to=hpa@zytor.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=john@grabjohn.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 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.