From: Giovanni Biscuolo <g@xelera.eu>
To: Alex Vong <alexvong1995@gmail.com>, guix-devel@gnu.org
Subject: Re: Suggest another way of importing GNU Guix GPG key
Date: Sun, 30 Jun 2019 11:44:04 +0200 [thread overview]
Message-ID: <878stj2ysb.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <86mui02hpq.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 945 bytes --]
Hello Guix!
Alex Vong <alexvong1995@gmail.com> writes:
> One solution would be to download the keyring from
> <https://ftp.gnu.org/gnu/gnu-keyring.gpg> and verify the signature in
> the following way:
>
> $ gpg --keyring ./gnu-keyring.gpg --verify guix-1.0.1.tar.gz.sig guix-1.0.1.tar.gz
>
Correct, the quick and "dirty" workaround is **to stop using the SKS
network** and warn Guix users to **manually download** certificates
This means we should quckly patch Guix manual: I've no time to propose a
patch today, I'll work on this tomorrow
We also nees to address this for **all** guix contributors: we require a
GPG signed commit, so each and every contributor/developer should
understand the risks of using SKS network and apply current proposed
workarounds: can we state this in maintenance.git/HACKING?
We sould act qulckly, IMHO
Thanks! Gio'
[...]
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-06-30 9:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-29 21:11 Suggest another way of importing GNU Guix GPG key dftxbs3e
2019-06-29 21:40 ` Alex Vong
2019-06-29 21:57 ` Christopher Lemmer Webber
2019-06-30 9:44 ` Giovanni Biscuolo [this message]
2019-07-02 15:54 ` Leo Famulari
2019-07-03 18:13 ` Leo Famulari
2019-07-13 18:29 ` Leo Famulari
2019-07-17 20:40 ` dftxbs3e
2019-07-18 8:03 ` Ricardo Wurmus
2019-07-18 8:58 ` Julien Lepiller
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=878stj2ysb.fsf@roquette.mug.biscuolo.net \
--to=g@xelera.eu \
--cc=alexvong1995@gmail.com \
--cc=guix-devel@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.
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.