public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xan <DXpublica@telefonica.net>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [kernel.org] md5 for verifying downloads of kernel [right post]
Date: Tue, 6 Apr 2004 10:26:05 +0200	[thread overview]
Message-ID: <200404061026.05377.DXpublica@telefonica.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0404052150570.13902-100000@coffee.psychology.mcmaster.ca>

Dimarts 06 Abril 2004 03:52, en/na Mark Hahn (<Mark Hahn 
<hahn@physics.mcmaster.ca>>) va escriure:
> > Is it possible to put in webpage and in ftp a link and a file,
> > respectively, of the md5 sums (or any other checking file program) of all
> > kernel files?.
>
> why are you not satisfied with the current GnuPG signatures on
> kernel tars and patch files?
>
> ie
> ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.1.tar.gz.sign
>
> > With this, anyone could see if the downloaded kernel file (usually more
> > than 30MB) is well-downloaded.
>
> indeed, tars and patches have been signed for a long time.

Okay. I did not know that. Now I satisfied ;-). But, I think a "miss": the 
webmaster of kernel.org could link the signature of all kernel files (?). 
That is, could we have got something like:

The latest stable version of the Linux kernel is:  	2.6.5 	2004-04-04 04:17 
UTC 	F 	V 	VI 	C 	Changelog SIGN

where SIGN links to 2.6.5 signature?

Sorry, but I think that the reference to signature page in kernel.org is not 
of all visible. It's in a more low possition, I think.

Sorry for ask that,
Xan.

       reply	other threads:[~2004-04-06  8:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0404052150570.13902-100000@coffee.psychology.mcmaster.ca>
2004-04-06  8:26 ` Xan [this message]
2004-04-05 13:33 [kernel.org] md5 for verifying downloads of kernel [right post] Xan
2004-04-05 16:06 ` H. Peter Anvin

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=200404061026.05377.DXpublica@telefonica.net \
    --to=dxpublica@telefonica.net \
    --cc=hahn@physics.mcmaster.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox