tion!
So here is the solution summary:
This line:
> export PINENTRY_KDE_USE_WALLET=1
>
Should be put in a script located at:
> $HOME/.config/plasma-workspace/env
For eg:
> $HOME/.config/plasma-workspace/env/pinentry-kde-fix.sh
Should *not* be present inside ~/.bashrc else it won&#
ferred https://wiki.archlinux.org/title/GnuPG#pinentry so I
> switched between pinentry, pinentry-gnome3, -gtk, -qt, -qt5, but it didn't
> work.
>
> Then I added in ~/.bashrc this: (and also checked https://dev.gnupg.org/D599
> for any syntax issue)
>
> > export PINENTRY
I'm using KDE Plasma 6.2.0
I have disabled KDE Wallet integration.
I have enabled KeepassXC's Secret Integration.
I'm using Endeavour OS which is arch based.
Earlier I referred https://wiki.archlinux.org/title/GnuPG#pinentry so I
switched between pinentry, pinentry-gnome3, -gtk, -q
On Sonntag, 13. Oktober 2024 10:32:01 MESZ Mihir Rabade via Gnupg-users wrote:
> I have configured git commit signing, which uses gpg. While trying to
> commit, a pinentry gui popup comes up where I enter the password for my gpg
> key.
> I also configured KeepassXC's Freedeskt
Hello!
I have configured git commit signing, which uses gpg. While trying to
commit, a pinentry gui popup comes up where I enter the password for my gpg
key.
I also configured KeepassXC's Freedesktop secret service integration to
save passwords after disabling kwallet & uninstall
rectory of the distribution.
> So I guess I need to read a pile of manpages and figure out how
> to create a config file that tells gpg where things are. This is
> bizarre behavior on a UNIX/Linux system where I guess the PATH
> just does not matter much. Then again I don't kn
* Dennis Clarke via Gnupg-users:
> I have no idea what you are talking about. That is not a manpage.
I can see that you have no idea. Look closely at the URL you posted [1],
and you will notice the infix "/manual/".
[1] https://www.gnupg.org/gph/en/manual/c14.html
What I wrote in my last mess
On 7/20/24 03:10, Andreas Metzler wrote:
On 2024-07-20 Dennis Clarke via Gnupg-users wrote:
Looking at https://www.gnupg.org/gph/en/manual/c14.html one would get
the idea that GPG would "just work" given that pinentry is right there
oberon$ which pinentry
/usr/local/bi
On 7/20/24 04:30, Ralph Seichter via Gnupg-users wrote:
* Dennis Clarke via Gnupg-users:
Looking at https://www.gnupg.org/gph/en/manual/c14.html one would get
the idea that GPG would "just work" given that pinentry is right there
in my PATH [...]
How would one get that idea? The m
* Dennis Clarke via Gnupg-users:
> Looking at https://www.gnupg.org/gph/en/manual/c14.html one would get
> the idea that GPG would "just work" given that pinentry is right there
> in my PATH [...]
How would one get that idea? The manual page you linked contains neither
the st
On 2024-07-20 Dennis Clarke via Gnupg-users wrote:
> Looking at https://www.gnupg.org/gph/en/manual/c14.html one would get
> the idea that GPG would "just work" given that pinentry is right there
> oberon$ which pinentry
> /usr/local/bin/pinentry
[...]
Hello,
afaik gnu
Looking at https://www.gnupg.org/gph/en/manual/c14.html one would get
the idea that GPG would "just work" given that pinentry is right there
in my PATH :
oberon$ which pinentry
/usr/local/bin/pinentry
oberon$
oberon$ ldd /usr/local/bin/pinentry
linux-vdso.so.1 (0x7f
Hi!
>- Sign git commits in WSL2(Debian)
>- gpg-agent uses Gpg4win's pinentry GUI to allow PIN entry
So you are mixing Unix software with Windows software. I wonder that
this works at all. The properties of the IPC between Windows and Unix
are different. That IPC is not
Hello,
My use case is:
- Sign git commits in WSL2(Debian)
- gpg-agent uses Gpg4win's pinentry GUI to allow PIN entry
This works well immediately after restarting my Windows PC. However, after
the PIN cache expires (currently set to 86400 seconds), signing commits
fails with
>
El día viernes, mayo 17, 2024 a las 01:39:55 +0900, NIIBE Yutaka escribió:
> Hello,
>
> Matthias Apitz wrote:
> > This isn't that easy. The pcscd is running (when needed) as:
> >
> > purism@pureos:~$ ps ax | grep pcscd
> >2151 ?Ssl0:00 /usr/sbin/pcscd --foreground --auto-exit
> >
Hello,
Matthias Apitz wrote:
> This isn't that easy. The pcscd is running (when needed) as:
>
> purism@pureos:~$ ps ax | grep pcscd
>2151 ?Ssl0:00 /usr/sbin/pcscd --foreground --auto-exit
>
> it is launched by a system service:
I see. IIUC, PureOS is Debian based. There should
El día jueves, mayo 16, 2024 a las 04:09:44 +0900, NIIBE Yutaka escribió:
> Hello,
>
> Matthias Apitz wrote:
> > It seems that the first time is longer. I will increase the debug-level
> > for scdaemon.
>
> Thank you for the information. I think that it's better to debug how
> PC/SC goes.
>
>
Hello,
Matthias Apitz wrote:
> It seems that the first time is longer. I will increase the debug-level
> for scdaemon.
Thank you for the information. I think that it's better to debug how
PC/SC goes.
To get full debug log in lower level, you can invoke pcscd manually with
root:
# LIBCCID_
Hello,
I wonder if it taks always 8-9 secs, or it's only for the first time.
Matthias Apitz wrote:
> /tmp/scdaemon-debug.log:
[...]
> 2024-05-15 11:07:58 scdaemon[16983] DBG: chan_7 <- SERIALNO
>
> It takes 8 secs until scdaemon detects the reader, waht does this maen?
>
> 2024-05-15 11:08:06 sc
El día jueves, mayo 16, 2024 a las 03:00:52 +0900, NIIBE Yutaka escribió:
> Hello,
>
> I wonder if it taks always 8-9 secs, or it's only for the first time.
>
> Matthias Apitz wrote:
> > /tmp/scdaemon-debug.log:
> [...]
> > 2024-05-15 11:07:58 scdaemon[16983] DBG: chan_7 <- SERIALNO
> >
> > It
Hello,
I'm using an OpenPGP card in my cellphone Puris L5 for GnuPG
actions (password-store, SSH, ...). It mostly takes some 8-9 seconds
until the PIN entry dialog pops up. I enabled debug log for the
gpg-agent and the scdaemon, see below, and the time is consumed
by the scdaemon waitinng for some
Hello,
Your configuration of pinentry-program is:
Caleb Herbert wrote:
> /gnu/store/rfy36kapnhx9djhxdi3a54x5p2n097xv-pinentry-gtk2-1.2.1/bin/pinentry-gtk-2
But what you tested in your command line is:
> /gnu/stor/gnu/store/rfy36kapnhx9djhxdi3a54x5p2n097xv-pinentry-gtk2-1.2.1/bin/pinent
OS: GNU Guix System
caleb@miller ~🍁 which pinentry
/home/caleb/.guix-home/profile/bin/pinentry
caleb@miller ~🍁 cat ~/.gnupg/gpg-agent.conf
Werner Koch via Gnupg-users wrote in
<87r0lhzxgu@jacob.g10code.de>:
|On Wed, 25 Oct 2023 18:51, Michael Richardson said:
...
|Use a different home directory. Actually running
| gpg --homedir /somewhere -s something
|should be enough but the agent and dirmngr started on the fly won't be
Hi Ingo,
actually I could solve the problem now by placing the gpg-agent.conf
with the specification of the pinentry program into the folder I specify
as GNUPGHOME. I still don't understand why this is necessary, as my
normal home directory doesn't contain this file. But it is worki
pg: DBG: chan_4 <- ERR 67108949 No pinentry
> gpg: agent_genkey failed: No pinentry
> Key generation failed: No pinentry
I'm wondering why you have problems with something that I'm using almost daily
while working on Kleopatra. I do
GNUPGHOME=/somewhere gpg ...
or
GNUPGHOME=/somew
On Wed, 25 Oct 2023 18:51, Michael Richardson said:
> The gpg-agent dependancy that came a few years ago has really been a PITA.
a few years = 20 years [1]
> I would really like some way to tell GPG that it really needs to ignore all
> of *my* (personal) setup, because I'm wearing a different pe
Werner Koch via Gnupg-users wrote:
> On Wed, 25 Oct 2023 13:01, Falko Strenzke said:
>> Can anyone give me an advice what I can try to get the GnuPG Agent
>> pinentry working with different home directory specified via
>> GNUPGHOME?
> Run it this wa
On Wed, 25 Oct 2023 13:01, Falko Strenzke said:
> Can anyone give me an advice what I can try to get the GnuPG Agent
> pinentry working with different home directory specified via
> GNUPGHOME?
Run it this way:
mkdir /foo/bar
cd /foo/bar
GNUPGHOME=`pwd` gpg-agent --daemon ~/bin/gnupg-se
I am trying to run GnuPG with a different home directory by setting the
environment variable GNUPGHOME. However, in that case, for instance when
trying to generate a key, in that case I get the error
gpg: DBG: chan_4 <- ERR 67108949 No pinentry
gpg: agent_genkey failed: No pinentry
> On 2022-02-23 08:40, jman wrote:
I think you can set that with an env var in your ~/.bashrc:
export PINENTRY_USER_DATA=ncurses
and the pinentry chooser will be `/usr/bin/pinentry-ncurses`.
As a further option, I use the basic `tty` pinentry chooser and I set
this in my ~/.bashrc:
exp
> On 2022-02-23 11:40, Klaus Ethgen wrote:
Am Di den 22. Feb 2022 um 17:28 schrieb Fourhundred Thecat via Gnupg-users:
How can I confugure so that the ncurses (text based) dialog is used
instead ?
You should be able to call it this way:
env -u DISPLAY gpg -c foo
that works!
thank you
Am Di den 22. Feb 2022 um 17:28 schrieb Fourhundred Thecat via Gnupg-users:
> the GUI pinentry dialog pops up to ask for password (I guess its
> pinentry-gtk-2)
>
> How can I confugure so that the ncurses (text based) dialog is used
> instead ?
You should be able to call it this
> On 2022-02-23 07:05, Fourhundred Thecat via Gnupg-users wrote:
> On 2022-02-22 18:57, john doe via Gnupg-users wrote:
On 2/22/2022 5:28 PM, Fourhundred Thecat via Gnupg-users wrote:
$ update-alternatives --config pinentry
What I would like to achieve is, that only when I call gog fr
fig pinentry
thank you, but changing this globally unfortunately causes problem with
thunderbird/enigmail. I get this error when trying to open encrypted mail:
Your GnuPG installation is configured to use the console for pinentry.
However, when using Enigmail you need a graphical version of pinen
El día martes, febrero 22, 2022 a las 05:28:00p. m. +0100, Fourhundred Thecat
via Gnupg-users escribió:
> Hello,
>
> when I type a gpg command in the terminal, such as:
>
> gpg -c foo
>
> the GUI pinentry dialog pops up to ask for password (I guess its
> pinent
It's not ncurses, but you can use 'gpg --pinentry-mode loopback' to get the
text mode.
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg.org/mailman/listinfo/gnupg-users
On 2/22/2022 5:28 PM, Fourhundred Thecat via Gnupg-users wrote:
Hello,
when I type a gpg command in the terminal, such as:
gpg -c foo
the GUI pinentry dialog pops up to ask for password (I guess its
pinentry-gtk-2)
How can I confugure so that the ncurses (text based) dialog is used
Hello,
when I type a gpg command in the terminal, such as:
gpg -c foo
the GUI pinentry dialog pops up to ask for password (I guess its
pinentry-gtk-2)
How can I confugure so that the ncurses (text based) dialog is used
instead ?
I am using gpg 2.2.12 on Debian 10
thank you
est is to run "xfd" If it runs and tells you no "no font to
display" you can run X programs (like pinentry-gtk) on the remote box.
If you do not fully trust the remote machine (and only then you should
use X forwarding), you may still use gpg/gpgsm on the remote box:
Hi
I have a very basic gnupg setup on a remote server, with the following options
set for the gpg-agent. Please cc me on the replies since I have not subscribed.
#pinentry-program /usr/bin/pinentry-curses
#pinentry-program /usr/bin/pinentry-tty
#pinentry-program /usr/bin/pinentry-qt
#pinentry
On 12/30/21 17:44, Ingo Klöcker wrote:
On Donnerstag, 30. Dezember 2021 15:38:47 CET Lars Noodén via Gnupg-users
wrote:
What else is needed to get pinentry invoked so that the SSH client can
connect using the GnuPG RSA key?
At this point the public key is visible in the SSH agent:
$ ssh
On Donnerstag, 30. Dezember 2021 15:38:47 CET Lars Noodén via Gnupg-users
wrote:
> What else is needed to get pinentry invoked so that the SSH client can
> connect using the GnuPG RSA key?
>
> At this point the public key is visible in the SSH agent:
>
> $ ssh-add -l
>
rased everything and started over with a newly created client-side
account and updated authorized_keys on the server. Some step is missing
and I cannot figure out how to get pinentry involved to make the key
available for the SSH client to use again.
What else is needed to get pinentry invoked so
> On 31. 5. 2021, at 12:30, Andreas Mattheiss
> wrote:
>
> I don't have any pinentry defined in any of my settings in .gnupg/ neither.
FYI for the archives, this was the problem. ~/.gnupg/gpg-agent.conf had the
following entry:
pinentry-program
/usr/local/MacGPG2/libexec
ccording to my old binary. The build
>> seems fine, but ...
>>
> The obvious thing would be to also update pinentry, which is painless.
I should have mentioned this, but it was a new build of pinentry, too. However,
since the README said that pinentry wasn’t required for the build, I
but if your pinintry is also as of 2013 there might
(might!) be incompatabilities with a modern gpg? The obvious thing would
be to also update pinentry, which is painless.
You can specify a pinentry program during the configure step when building
gpg. I haven't done this, and it still finds p
"Christopher W. Richardson "
gpg: using "04B90F4FA999D22FBFB769773FAE5104E3874F31" as default secret key for
signing
gpg: public key decryption failed: No pinentry
gpg: decryption failed: No pinentry
cwr@cwr2019mbp passwds % which pinentry
/usr/local/bin/pinentry
cwr@cwr2019mb
ool NO
To remove any saved passwords from macOS Keychain, search
for GnuPG to find them.
The folks of homebrew are using our version of pinentry which is
based off the standard pinentry, but adds the possibility to store passphrases
for GnuPG keys in macOS Keychain. For our version of GnuPG it
On Tue, 16 Mar 2021 20:34, Klaus Ethgen said:
> I believe, it is the "no-allow-external-cache" option.
Right, but I am not sure about the macOS pinentry; in particular if it
is closely based on the standard pinentry code base or does its own
thing. Any pointer to that pinentry?
Hi,
Am Di den 16. Mär 2021 um 17:19 schrieb Mark McDonnell via Gnupg-users:
> It would be great if users could configure the default as it feels
> dangerous to default to saving the passphrase.
I believe, it is the "no-allow-external-cache" option.
I had the same on linux with the shity gnome PW
; associated numbers - It is the fifth element in —with-key-data but I don’t
> recognize it.
>
> This default for pin entry is … frustrating.
>
> Regards,
>
> bex
> On Mar 16, 2021, 12:05 PM +0100, Mark McDonnell via Gnupg-users <
> gnupg-users@gnupg.org>, wrote:
>
, wrote:
> Hi,
>
> The default behaviour of the pinentry app (on macOS at least) is to have the
> option "save password in Keychain" automatically selected.
>
> I have to deselect this every time I use a specific GPG key where I don't
> want the password saved in
Hi,
The default behaviour of the pinentry app (on macOS at least) is to have
the option "save password in Keychain" automatically selected.
I have to deselect this every time I use a specific GPG key where I don't
want the password saved in the macOS Keychain. Unfortunately it se
On Tue, 2 Mar 2021 10:35, Romain Lebrun Thauront said:
> So, is there a way to have BOTH gpg-agent managing ssh, and GTK
> pinentry prompts for unlocking keys ?
I use this for more than a decade. You have to use
gpg-connect-agent updatestartuptty /bye
if you switch your xserver; that
now "link" to the last
> terminal I opened, and I do not have the GTK's
> Pinentry prompt.
> It's very annoying as I use a lot of terminal, and some graphic software like
> thunderbird will not trigger the GTK
> prompt to unlock my GPG key anymore. (Therefore hangi
d I do not have the GTK's Pinentry prompt.
It's very annoying as I use a lot of terminal, and some graphic software like
thunderbird will not trigger the GTK prompt to unlock my GPG key anymore.
(Therefore hanging indefinitely in the hope to receive access to my GPG private
key, which th
On Wed Feb 17, 2021 at 11:37 AM CET, Werner Koch wrote:
> FWIW: We do not provide a pinentry under that name. This must be a
> homebrew specific change which unfortunately is not reflected by the
> version number.
I looked up `pinentry-mac` via Homebrew website[1] to see who is the
main
On Mon, 15 Feb 2021 16:23, Ondřej Synáček said:
> pinentry-mac (pinentry) 1.1.0
> Copyright (C) 2016 g10 Code GmbH
FWIW: We do not provide a pinentry under that name. This must be a
homebrew specific change which unfortunately is not reflected by the
version number.
The latest pinen
On Mon Feb 15, 2021 at 4:16 PM CET, Lukas Pitschl wrote:
> Are you using the full path in your gpg-agent.conf?
> `pinentry-program /usr/local/bin/pinentry-mac`
Yes that is how I specified it, exactly like that.
> You might also try calling `/usr/local/bin/pinentry-mac —version` and
>
Hi Ondřej,
> I’m not sure what happened in past day or so but when I set
> `pinentry-program` in my
> `gpg-agent.conf` to value `pinentry-mac`,
Are you using the full path in your gpg-agent.conf?
`pinentry-program /usr/local/bin/pinentry-mac`
You might also try calling `/usr/local/bin
Hello. I’m a mac user and I am using `pinentry-mac` via homebrew. The
homebrew package
links to repository for `pinentry` so that is why I am asking here (not
sure if that
specific port is maintained by somebody).
I’m not sure what happened in past day or so but when I set
`pinentry-program
Hi,
The GnuPG project is pleased to announce the availability of the latest
release of the collection of PIN or passphrase entry dialogs for GnuPG,
Pinentry 1.1.1.
Noteworthy changes in version 1.1.1 (2021-01-21)
===
* A Pinentry for the Enlightenment
Dear gnupg users,
the pinetry-qt window now shows up again, behind other windows...
Sorry for the noise, Gregor
* Gregor Zattler [21. Dez. 2020]:
> Dear gnupg users, since Friday pinentry-{qt,gtk2,gnome3}
> stopped working. When I want to decrypt some .gpg file, no dialog
> appear
Dear gnupg users, since Friday pinentry-{qt,gtk2,gnome3}
stopped working. When I want to decrypt some .gpg file, no dialog
appears and gpg-agent times out. Luckily pinentry-curses and
pinentry-fltk still do work.
This is on a debian buster system with gpg* packages from backports,
pinentry
Hello,
I just upgraded to Debian bullseye and the graphical pinentry did not work
anymore. I got the following error message:
2020-11-28 21:37:41 gpg-agent[3535] DBG: connection to PIN entry established
2020-11-28 21:37:41 gpg-agent[3535] DBG: chan_10 -> INQUIRE PINENTRY_LAUNCHED
3633 g
tuptty /bye >/dev/null
Now, when I try to decrypt a file on the remote machine, pinentry opens a
dialog on the local machine.
If the password is properly typed, the decrypted file is printed out on the
remote machine!
This took quite a while to figure out!
THANK YOU!
Oz
--
---
Imag
extra
```
A.
On 03/11/2020 20:29, Oz Tiram via Gnupg-users wrote:
> ~$ cat .gnupg/gpg.conf
> use-agent
> pinentry-mode loopback
> ~$ cat .gnupg/gpg-agent.conf
> pinentry-program /usr/bin/pinentry
> no-grab
> default-cache-ttl 1800
> enable-ssh-support
> allow-loopback-
uccess. I
have 2 Debian testing machine with GPG version:
~$ gpg --version
gpg (GnuPG) 2.2.20
libgcrypt 1.8.6
GPG agent should be forwarded from one machine (local) to the other
(remote). On the local machine, I have the following settings:
~$ cat .gnupg/gpg.conf
use-agent
pinentry-mode loo
Apologies, I accidentally posted the complete SO question in my previous
email.
That was not my intention. I hope I can still find some answers with the
help from subscribers of this list.
Best wishes
Oz
--
---
Imagine there's no countries
it isn't hard to do
Nothing to kill or die for
And no
fyi; maybe it's a change somewhere in GnuPG land?
- Forwarded message from Matthias Apitz -
Date: Sat, 22 Feb 2020 10:11:20 +0100
From: Matthias Apitz
To: jh...@freebsd.org, freebsd-po...@freebsd.org
Subject: security/pinentry-qt5
Hello,
I use security/pinentry-qt5 in KD
On Mon, 16 Dec 2019 14:01:22 -0500
Daniel Kahn Gillmor wrote:
>On Mon 2019-12-16 13:39:10 +0100, Andreas Ronnquist wrote:
>> Changing to pinentry-gtk3 also removes the problem, and that is an
>> acceptable solution for me, so I have no hurry in getting fixes to
>> the gtk-2
On Mon 2019-12-16 13:39:10 +0100, Andreas Ronnquist wrote:
> Changing to pinentry-gtk3 also removes the problem, and that is an
> acceptable solution for me, so I have no hurry in getting fixes to the
> gtk-2 version.
just to clarify, i think you're talking about pinentry-gnome3, no
;>> I have my gpg key on a card (a Librem key, which basically is a
>>> Nitrokey) when using pinentry to enter the card password, I first
>>> have to press my mouse on the screen (or a key on my keyboard) to
>>> make the password dialog appear.
>>
&g
On Mon, 16 Dec 2019 10:47:32 +0900
NIIBE Yutaka wrote:
>Andreas Ronnquist wrote:
>> I have a problem on Debian unstable (running in Virtualbox), running
>> the Xfce desktop -
>>
>> I have my gpg key on a card (a Librem key, which basically is a
>> Nitrokey)
Andreas Ronnquist wrote:
> I have a problem on Debian unstable (running in Virtualbox), running the
> Xfce desktop -
>
> I have my gpg key on a card (a Librem key, which basically is a
> Nitrokey) when using pinentry to enter the card password, I first have
> to press my mouse
Hi!
I have a problem on Debian unstable (running in Virtualbox), running the
Xfce desktop -
I have my gpg key on a card (a Librem key, which basically is a
Nitrokey) when using pinentry to enter the card password, I first have
to press my mouse on the screen (or a key on my keyboard) to make
On Mon, 25 Nov 2019 08:44, Werner Koch said:
> Thanks. I don't see that INSIDE_EMACS is propagated and I can duplicate
My fault. We pass the the envvars to pinentry using setnev in an atfork
handler. Thus we do not see them in the Assuan log. I added some
logging to so that we can
* Werner Koch:
> I will look into this today so that a possible fix can go into 2.2.18.
Thanks a lot, Werner.
-Ralph
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
On Sat, 16 Nov 2019 18:22, Ralph Seichter said:
> ipc". I added the latter, and the resulting log file is available via
> https://seichter.de/aegi6bee9eShu/gpg-agent.log . Note that I killed
Thanks. I don't see that INSIDE_EMACS is propagated and I can duplicate
that problem here. I will look i
* Ralph Seichter:
> https://seichter.de/aegi6bee9eShu/gpg-agent.log
Gentle bump, because I posted this a week ago. Did you have a chance to
examine the log, Werner?
-Ralph
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailm
* Werner Koch:
> You forgot to _add_
>
> debug-pinentry
> debug ipc
> verbose
>
> to gpg-agent.conf.
Here's the gpg-agent.conf I used:
default-cache-ttl
max-cache-ttl
no-allow-mark-trusted
enable-ssh-support
pinentry-program /home/xyz/bin/pinentry-wrap
On Fri, 15 Nov 2019 21:45, Ralph Seichter said:
> gpg-agent[27187]: failed to read the secret key
> gpg-agent[27187]: command 'PKDECRYPT' failed: Timeout
You forgot to _add_
debug-pinentry
debug ipc
verbose
to gpg-agent.conf. (The "debug ipc" is helpful be
d4700 for fd 12 terminated
[...]
I did try to enter my pass phrase, but my interpretation of the above
timeout is that my input never made it back to gpg-agent?
I am not quite sure how to best debug this further. In my OP I mentioned
trying to have pinentry in a separate, dedicated terminal? Is th
On Thu, 14 Nov 2019 19:54, Ralph Seichter said:
> $ cat /tmp/pinentry-wrapper.log
> INSIDE_EMACS is ''
Pinentry consideres that it is not run from Emacs and thus it does not
forward requests to Emacs but uses the standard pinentry (or should
return an error for pinentry-emacs
* Filipp Gunbin via Gnupg-users:
> I see this in NEWS for Emacs 27.1 (unreleased master).
>
> --8<---cut here---start->8---
> *** 'epa-pinentry-mode' is renamed to 'epg-pinentry-mode'.
> It now applies to epg function
* Werner Koch via Gnupg-users:
> ${TMPDIR-/tmp}/emacs$(id -u)/pinentry
The socket exists and the permissions look OK (read/write access for my
Linux user).
> If you insert a pinentry wrapper, can you see the INSIDE_EMACS envvar?
I just tried the following wrapper script:
#!/usr/bin/en
On 13/11/2019 17:58 +0100, Ralph Seichter wrote:
> * Filipp Gunbin via Gnupg-users:
>
>> I have 2.2.17 and it works with empty gpg-agent.conf and just this
>> line in .emacs:
>> (setq epg-pinentry-mode 'loopback)
>
> I use the same GnuPG version, but the Ema
NEWS for Emacs 27.1 (unreleased master).
--8<---cut here---start----->8---
*** 'epa-pinentry-mode' is renamed to 'epg-pinentry-mode'.
It now applies to epg functions as well as epa functions.
--8<---cut here-
6.
Fortunately I always use xterms so the regular GUI pinentry works
nicely. I only briefly tested the Emacs pinentry features we once
introduced for epg.
The socket used by pinentry-emacs is
${TMPDIR-/tmp}/emacs$(id -u)/pinentry
does this exist? If you insert a pinentry wrapper, c
* raf via Gnupg-users:
> Wherever it needs to be to get added to the gpg command line when
> invoked from within emacs.
As far as I can tell, that's what epa-pinentry-mode is used for (which I
tried unsuccessfully, as stated in my OP). I think I have tried every
EasyPG trick and work
Ralph Seichter wrote:
> * raf via Gnupg-users:
>
> > Does "--pinentry-mode loopback" make any difference?
>
> Where exactly do you suggest I add this option?
>
> -Ralph
Wherever it needs to be to get added to the gpg command line
when invoked from withi
* Filipp Gunbin via Gnupg-users:
> I have 2.2.17 and it works with empty gpg-agent.conf and just this
> line in .emacs:
> (setq epg-pinentry-mode 'loopback)
I use the same GnuPG version, but the Emacs variable setting you
suggested makes no difference for me. That's Emacs ve
* raf via Gnupg-users:
> Does "--pinentry-mode loopback" make any difference?
Where exactly do you suggest I add this option?
-Ralph
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Which version of GnuPG are you using? I have 2.2.17 and it works with
empty gpg-agent.conf and just this line in .emacs:
(setq epg-pinentry-mode 'loopback)
Filipp
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/ma
ntil I encounter signed or encrypted mail (GPG and/or
> S/MIME). Emacs attempts to prompt me for my password, or to ask me
> whether I trust signator XYZ, but crams that prompt into the last two
> lines of the Emacs window, so I cannot really see what is expected of
> me.
>
> I
pt me for my password, or to ask me
whether I trust signator XYZ, but crams that prompt into the last two
lines of the Emacs window, so I cannot really see what is expected of
me.
I use gpg-agent and have tried both pinentry-tty and pinentry-curses. I
tried with and without 'allow-emacs-pinent
n which process can put
> itself into the focus. Enigmail needs to tell Pinentry, via gpg, that
> it may take the focus and request input. This is implemented by a
> callback mechanism all the way from Pinentry, via gpg-agent and gpg up
> to the calling process (Thunderbird here).
>
Hi!
Here is my reply to the Enigmail list which explains why this is indeed
not just a problem of gpg and that we can't have a perfect solution.
For security reasons Windows has strict rules on which process can put
itself into the focus. Enigmail needs to tell Pinentry, via gpg, that
i
I have asked this in the enigmail mailing list and was referred to GNUPG
but Patrick Brunschwig:
> On 26.11.18 09:33, Bernhard Kleine wrote:
>> I use enigmail with thunderbird 60.3.1 on win7. Enigmail asks me
>> regularly for the passphrase via pinentry since I sign my mails.
1 - 100 of 482 matches
Mail list logo
