From: "Gábor Boskovits" <boskovits@gmail.com>
To: Marco van Hulten <marco@hulten.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: gpg-agent error: No pinentry
Date: Fri, 20 Dec 2019 20:12:30 +0100 [thread overview]
Message-ID: <CAE4v=pjJbNU57zEY1TqbPg6YT=3cLixQzoEY+KXdSJ=MkN5Fgw@mail.gmail.com> (raw)
In-Reply-To: <20191220104927.1533364a@gfi063209.klientdrift.uib.no>
Hello Marco,
Marco van Hulten <marco@hulten.org> ezt írta (időpont: 2019. dec. 20.,
P, 10:49):
>
> Following up on my pinentry issue—
>
> In the end I used a work-around. I decrypted the sensitive file on an
> off-line OpenBSD machine onto a mounted USB flash drive, then mounted
> the drive to the Guix machine, did what I needed to do with the file,
> shredded any copy of the file and finally removed the USB drive and
> destroyed it with a hammer.
I am sorry that this ended up like this.
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?
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 on this particular machine, the related
config items look like:
(define gpg-agent.conf
(plain-file "gpg-agent.conf" "
pinentry-program /home/<username>/.guix-profile/bin/pinentry
"))
and
(home
(data-directory "/data/<username>")
(configurations
(list (simple-file-home gpg-agent.conf
".home-config/.gunpg/gpg-agent.conf"))))
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.
>
> —Marco
>
Best regards,
g_bor
--
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21
next prev parent reply other threads:[~2019-12-20 19:12 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 [this message]
2019-12-20 21:15 ` Marco van Hulten
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='CAE4v=pjJbNU57zEY1TqbPg6YT=3cLixQzoEY+KXdSJ=MkN5Fgw@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=help-guix@gnu.org \
--cc=marco@hulten.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).