From: Russell King <rmk@arm.linux.org.uk>
To: Valdis.Kletnieks@vt.edu
Cc: Chris Friesen <cfriesen@nortelnetworks.com>,
linux-kernel@vger.kernel.org
Subject: Re: kernel.org frontpage
Date: Wed, 29 Jan 2003 19:37:50 +0000 [thread overview]
Message-ID: <20030129193750.D6261@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200301291855.h0TItM4K007010@turing-police.cc.vt.edu>; from Valdis.Kletnieks@vt.edu on Wed, Jan 29, 2003 at 01:55:22PM -0500
On Wed, Jan 29, 2003 at 01:55:22PM -0500, Valdis.Kletnieks@vt.edu wrote:
> Yes, an intruder could leave a forged signature with a random key
> easily. But to leave a forged signature with the key that's already
> on my keyring is a lot harder...
I believe a script signs the files on ftp.kernel.org, which means the
private key is on the master machine, probably without a pass phrase.
That means that if the master server is compromised, its highly likely
that a rogue file will have a correct signature.
As hpa says, the GPG signature provides no assurance that Linus put
up patch-2.5.60.bz2 and not some random other person.
The only way to be completely sure is for Linus to gpg-sign the patches
himself at source with a known gpg key using a secure pass phrase before
they leave his machine (preferably before the machine is connected to
the 'net to upload them for the really paranoid.)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-01-29 19:28 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
2003-01-29 18:36 ` Chris Friesen
2003-01-29 18:55 ` Valdis.Kletnieks
2003-01-29 19:37 ` Russell King [this message]
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=20030129193750.D6261@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=Valdis.Kletnieks@vt.edu \
--cc=cfriesen@nortelnetworks.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.