all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, Polchi <polchi.dabarov@riseup.net>
Subject: Re: Torrenting GuixSD!
Date: Wed, 25 Feb 2015 18:51:56 +0100	[thread overview]
Message-ID: <20150225175156.GA6653@debian.math.u-bordeaux1.fr> (raw)
In-Reply-To: <87oaoidn19.fsf@netris.org>

On Wed, Feb 25, 2015 at 10:32:50AM -0500, Mark H Weaver wrote:
> If we were to extend this argument to non-torrent downloads, then all
> of our downloads (source tarballs and images) should be tar files
> containing a signature bundled with the thing being signed.  mit-krb5
> follows this policy with their source tarballs.

No, extending this argument to non-torrent downloads means that we should
advertise the signature next to the actual file. This holds on the gnu ftp
servers, where alphabetical ordering ensures they are next to each other.
And it usually holds on web sites. In both cases, there is almost no extra
effort for downloading the signature.

Alternatively in our case, since the torrent file also needs to be downloaded
from somewhere, it would make sense to put the signature file next to the
torrent file on the download site.

Andreas

  reply	other threads:[~2015-02-25 17:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13 17:23 Torrenting GuixSD! Polchi
2015-02-13 22:53 ` David Thompson
2015-02-14  2:50   ` Eric Bavier
2015-02-23 20:47     ` Ludovic Courtès
2015-02-23 20:54       ` Andreas Enge
2015-02-25 14:00         ` Ludovic Courtès
2015-02-25 14:12           ` Andreas Enge
2015-02-25 15:32             ` Mark H Weaver
2015-02-25 17:51               ` Andreas Enge [this message]
2015-02-25 21:47                 ` Ludovic Courtès
2015-02-25 21:51                   ` Andreas Enge
2015-02-14  9:30 ` Andreas Enge

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=20150225175156.GA6653@debian.math.u-bordeaux1.fr \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.org \
    --cc=polchi.dabarov@riseup.net \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.