unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-science@gnu.org
Subject: Re: Help! I messed up guix-past
Date: Sat, 10 Sep 2022 18:20:44 +0200	[thread overview]
Message-ID: <m17d2b6w0z.fsf@fastmail.net> (raw)
In-Reply-To: <868rmr7e81.fsf@gmail.com>

Hi Simon and Ludo,

zimoun <zimon.toutoune@gmail.com> writes:

> I do not know.  For now, nothing is “broken” and I get:
>
> --8<---------------cut here---------------start------------->8---
> $ cat /tmp/channels.scm
> (cons*
>  (channel
>   (name 'past)
>   (url "https://gitlab.inria.fr/guix-hpc/guix-past.git")
>   (branch "master"))
>  %default-channels)

Your channel definition doesn't include the introduction, so it's normal
that you have no authentication issues - you are using guix-past
unauthenticated. That's also what I am doing at the moment, as a
workaround.

Ludovic Courtès <ludovic.courtes@inria.fr> writes:

> I understand the feelings—OpenPGP in general but also GPG make for a
> unpleasant user experience coupled with a steep learning curve, and few
> reach the top of that curve (I haven’t).

Me neither (and I am not motivated to get there). But it's worse for me,
because I have no password protection on my keys. Anyone who grabs my
laptop can do whatever they like with my keys. Or rather "could",
because I have moved everything to an encrypted disk partition that I
mount only when required. But that's a real pain to use.

I spent a lot of time on this problem, and reached the conclusion that
it's the existence of two different versions of GnuPG that causes the
trouble. GnuPG then picks up the wrong version of gpg-agent, discovers a
version mismatch, and gives up on password checking. A rather strange
way to handle security!

Unfortunately I can't uninstall either of my two versions. One is from
Ubuntu, the other from Guix, and both are dependencies of other packages
in their respective package universes. Even running GnuPG in a container
doesn't help.

Cheers,
  Konrad


  reply	other threads:[~2022-09-10 16:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 15:16 Help! I messed up guix-past Konrad Hinsen
2022-09-09 15:36 ` Ricardo Wurmus
2022-09-09 15:46 ` zimoun
2022-09-09 16:10   ` Konrad Hinsen
2022-09-09 17:39     ` zimoun
2022-09-10  7:39       ` Konrad Hinsen
2022-09-10  9:47         ` zimoun
2022-09-10 16:20           ` Konrad Hinsen [this message]
2022-09-11 14:07             ` Ludovic Courtès
2022-09-11 15:19               ` Efraim Flashner
2022-09-12  6:16               ` Konrad Hinsen
2022-09-12 15:26                 ` Ludovic Courtès
2022-09-13  8:58                   ` Konrad Hinsen
2022-09-13  9:23                     ` Ricardo Wurmus
2022-09-14  9:31                       ` Konrad Hinsen
2022-09-10 10:27         ` Ludovic Courtès
2022-09-10 10:40           ` zimoun
2022-09-10 14:39             ` Ricardo Wurmus
2022-09-12 16:00               ` zimoun
2022-09-09 16:16 ` 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

  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=m17d2b6w0z.fsf@fastmail.net \
    --to=konrad.hinsen@fastmail.net \
    --cc=guix-science@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).