From: Leo Famulari <leo@famulari.name>
To: Catonano <catonano@gmail.com>,
Dmitry Nikolaev <cameltheman@gmail.com>,
help-guix <help-guix@gnu.org>
Subject: Re: guix hash of source from git repository.
Date: Tue, 21 Feb 2017 17:21:02 -0500 [thread overview]
Message-ID: <20170221222102.GC18231@jasmine> (raw)
In-Reply-To: <20170221215629.wqrvnhsmr4l5q7zs@wasp>
On Tue, Feb 21, 2017 at 09:56:29PM +0000, ng0 wrote:
> On 17-02-21 22:25:35, Catonano wrote:
> Please avoid doing the way described below though. Calculating it in
> advance is more secure and helps to prevent introducing errors. If
> there's a mismatch it shows an error.
>
> > Another option is to try to build the package with the wrong hash, wait for
> > the error message and copy the right hash from within the error message
> > itself. Lame, but hey
I agree with ng0. We should not do this when creating Guix packages.
The guix download code has a relatively rare "network signature" when
compared to things like a web browser or wget.
Someone could serve a different file when they detect use of the Guix
download tool, and if this makes it into a package definition, all of
our users would end up with the wrong software.
next prev parent reply other threads:[~2017-02-21 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 21:19 guix hash of source from git repository Dmitry Nikolaev
2017-02-21 21:25 ` Catonano
2017-02-21 21:56 ` ng0
2017-02-21 22:21 ` Leo Famulari [this message]
2017-03-06 10:55 ` Ludovic Courtès
2017-02-21 22:17 ` Leo Famulari
2017-02-22 8:23 ` Catonano
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170221222102.GC18231@jasmine \
--to=leo@famulari.name \
--cc=cameltheman@gmail.com \
--cc=catonano@gmail.com \
--cc=help-guix@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).