From: Marco van Hulten <marco@hulten.org>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: gpg-agent error: No pinentry
Date: Fri, 20 Dec 2019 22:15:14 +0100 [thread overview]
Message-ID: <20191220221514.65fca628@jasniac.instanton> (raw)
In-Reply-To: <CAE4v=pjJbNU57zEY1TqbPg6YT=3cLixQzoEY+KXdSJ=MkN5Fgw@mail.gmail.com>
Gábor—
Thank you for the help: the issue might have been solved, at least
sometimes (sort-of explanation follows)!
Je 20 dec 20:12 skribis Gábor:
> If you still have the patience to experiment a little could you try
> with pinentry-tty on the console and pinentry-gtk on a gui?
Yes, I just had a little bit of time before the new year. (Christmas is
a holiday, they say!)
> It might be a valuable experience, and a feedback that our simple
> pinentry is faulty in some ways.
>
> I have extracted the inforamtions from my config, and it looks like this:
>
> manifest: (specifications->manifest '("gnupg" "pinentry-tty"))
>
> I also use guix home-manager [...]
A guix home-manager sounds intriguing. I alluded to it once when
asking why we wouldn't define the state of the whole computing
environment. But it adds a layer of complexity and so I don't think it
would be very useful to use this to analyse the problem I'm having.
> I am using bash, and I also have:
>
> At the end of my .bashrc:
> export GPG_TTY=$(tty)
>
> And at the end of my .bash_profile:
>
> gpg-agent --options /home/gabriel/.home-config/.gnupg/gpg-agent.conf --daemon
>
> I believe that is all.
>
> Could you have a look if it works for you with these settings? Also,
> please not that these are for console only use, most probably some
> other tweaks are needed to use this form a gui.
Yes, this helps! That is, when I set GPG_TTY and started the gpg-agent
like this, 'gpg --import' and 'gpg -d' started to work without
complaining about pinentry. But then I tried the same as another user
and there it still complained. So I went back to the first user again,
removed the GPG_TTY variable and killed the gpg-agent, but now it does
not complain anymore about pinentry anymore at all.
I don't understand what's going on, but for now I'll just add the export
and gpg-agent commands in my .bashrc since that seemed to do the trick
at least once.
export GPG_TTY=$(tty)
gpg-agent --options ${HOME}/.gnupg/gpg-agent.conf --daemon
—Marco
next prev parent reply other threads:[~2019-12-20 21:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 21:41 gpg-agent error: No pinentry Marco van Hulten
2019-12-18 21:50 ` Andreas Enge
2019-12-19 8:22 ` Marco van Hulten
2019-12-19 9:02 ` Marco van Hulten
2019-12-20 9:49 ` Marco van Hulten
2019-12-20 19:12 ` Gábor Boskovits
2019-12-20 21:15 ` Marco van Hulten [this message]
2019-12-18 21:52 ` Gábor Boskovits
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=20191220221514.65fca628@jasniac.instanton \
--to=marco@hulten.org \
--cc=boskovits@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).