From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>, "Leo Famulari" <leo@famulari.name>
Cc: 46829@debbugs.gnu.org
Subject: bug#46829: `guix pull` uses incorrect certificate store
Date: Wed, 14 Apr 2021 21:57:03 +0200 [thread overview]
Message-ID: <bd2e02c02a294adce2c197060539d6c84af9538c.camel@telenet.be> (raw)
In-Reply-To: <87im4pf8cg.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
On Wed, 2021-04-14 at 12:50 +0200, Ludovic Courtès wrote:
> [...]
> > > We could also add a ‘--no-check-certificates’ option to ‘guix pull’.
> >
> > I think we should avoid adding "use insecure connection" options. Even
> > if the code itself is signed.
>
> “Insecure” is a strong word: it still prevents eavesdropping, which is
> the only property that matters in the presence of authenticated
> channels.
Maybe call the option '--tolerate-eavesdropping' then? That name:
* is technically correct
* doesn't suggest the option is "Insecure"
* but still sounds like something you don't want
* should be clear to people not knowing about TLS' PKI infrastructure,
‘will eventually’™ be replaced with GNS + <insert GNUnet protocol here> or
something like that, which wouldn't use such a centralised structure.
Thoughts?
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-04-14 19:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 10:27 bug#46829: Fresh install of 1.2.0 can't guix pull Christopher Baines
2021-02-28 11:06 ` Andreas Enge
2021-02-28 11:10 ` Andreas Enge
2021-03-01 10:15 ` Ludovic Courtès
2021-03-01 9:49 ` zimoun
2021-03-05 10:49 ` Christopher Baines
2021-03-01 10:19 ` Ludovic Courtès
2021-03-01 12:03 ` Andreas Enge
2021-03-17 14:36 ` Ludovic Courtès
2021-04-11 20:41 ` Leo Famulari
2021-04-12 1:29 ` Leo Famulari
2021-04-12 6:42 ` Leo Famulari
2021-04-12 8:30 ` Leo Famulari
2021-04-12 12:25 ` Ludovic Courtès
2021-04-12 17:15 ` Leo Famulari
2021-04-12 17:32 ` Leo Famulari
2021-04-13 8:12 ` Ludovic Courtès
2021-04-13 18:09 ` Leo Famulari
2021-04-21 13:14 ` Ludovic Courtès
2021-04-12 12:25 ` Ludovic Courtès
2021-04-12 17:02 ` Leo Famulari
2021-04-12 18:26 ` Leo Famulari
2021-04-13 17:47 ` Leo Famulari
2021-04-13 9:29 ` bug#46829: `guix pull` uses incorrect certificate store Ludovic Courtès
2021-04-13 17:44 ` Leo Famulari
2021-04-14 10:50 ` Ludovic Courtès
2021-04-14 19:57 ` Maxime Devos [this message]
2021-05-31 19:17 ` Leo Famulari
2021-04-10 19:02 ` bug#46829: Fresh install of 1.2.0 can't guix pull Leo Famulari
2021-04-10 19:45 ` Christopher Baines
2021-04-10 20:30 ` Leo Famulari
2021-04-10 21:09 ` Leo Famulari
2021-04-10 21:21 ` Christopher Baines
2021-04-10 22:54 ` Leo Famulari
2021-04-10 23:04 ` Leo Famulari
2021-04-10 23:13 ` Leo Famulari
2021-04-14 1:08 ` Leo Famulari
2021-04-14 9:44 ` François
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=bd2e02c02a294adce2c197060539d6c84af9538c.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=46829@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).