unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Alex Kost <alezost@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Packaging packages with GPG signed source archives
Date: Wed, 31 Aug 2016 10:33:54 +0300	[thread overview]
Message-ID: <87oa49crz1.fsf@gmail.com> (raw)
In-Reply-To: <cu7d1kpv6qc.fsf@systemreboot.net> (Arun Isaac's message of "Wed, 31 Aug 2016 11:07:47 +0530")

Arun Isaac (2016-08-31 08:37 +0300) wrote:

> I am trying to package a package that provides a GPG signed source
> archive. Is there any way to get Guix to verify this signature, by say,
> specifying it in the 'origin' object of the 'source' field of the
> package? What is the standard way this is done in Guix?

I think the procedure is: a packager verifies the source and that's it.
Since a package has a hash of the source, we can be sure that the source
wasn't changed since it was packaged, so if we find that a package has
a compromised source, we can blame the packager.

-- 
Alex

  reply	other threads:[~2016-08-31  7:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31  5:37 Packaging packages with GPG signed source archives Arun Isaac
2016-08-31  7:33 ` Alex Kost [this message]
2016-08-31  7:47   ` Arun Isaac
2016-08-31 10:00     ` ng0
2016-08-31 17:22     ` Leo Famulari
2016-08-31 18:37       ` Arun Isaac
2016-08-31 20:21         ` Ludovic Courtès
2016-08-31 20:42           ` Troy Sankey
2016-09-01  8:29             ` Ludovic Courtès
2016-08-31 21:53           ` ng0
2016-09-01  8:30             ` Ludovic Courtès
2016-09-02 10:10               ` ng0
2016-09-02 12:14                 ` Ludovic Courtès
2016-09-02 12:46                   ` ng0

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=87oa49crz1.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=arunisaac@systemreboot.net \
    --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).