Right, you need a newer gnupg. Pinentry has no i18n support, thus your tests
are pointless.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Sep 28 2010
Fixed in SVN for a very long time.
This was already fixed the day after the release. Please check the SVN or the
recently published release candidate.
Sep 27 2010
Fix confirmed. Tested with gpg4win 2.1.0-svn1569.
So resolved.
Sep 24 2010
This is not a bug but expected behaviour: We want to show the pinentry on the
correct xserver or tty and thus gpg-needs to know which one it is. The manual
has even a hint how to show the pinentry on the client machine:
Yep, there is a bug in gpg-agent. Fixed for 2.0 in svn rev 5423. Patch for
gpg4win commited.
Sep 23 2010
Test works also for gpg4win 2.1.0-beta1 if created an empty file gpg-agent.conf
before gpg-agent is started:
There seems to be a relation if gpg-agent.conf exists or not.
I checked again: I can see no changes in my working copy since 2.0.16.
Just to note:
I tested with the debian package pinentry-qt (0.8.0.svn234-0kk1) from
files.kolab.org. It's the same problem with pinentry-qt and pinentry-gtk (see
test below).
You wrote that pinentry-qt works corectly since 0.8.0 (=svn222). I can't confirm
this with my test below. Or do you mean, that the additional changes in gnupg
are required for show the german "Abbrechen" button text in pinentry-qt?
My retest with gnupg 2.0.16...
Sep 22 2010
I have meanwhile switched to Gentoo on my notebook and tried again. The problem
still exists in 2.0.16. At first, the reader didn't work at all without pcscd,
but when I edited the source code so cherry_mode is not being set to 1, I could
at least use the reader again. The keypad is still being ignored though.
Please run my tests.
Sorry, the "set GPG_AGENT_INFO..." line was pasted from my windows test. My
GNU/Linux test starts of course with:
What do you think
There are actually two problems here.
Sep 17 2010
$ gpg-agent --version
gpg-agent (GnuPG) 2.0.16
Do you have a pinentry installed? Depending on your configuraion the default is
either /usr/bin/pinentry or /usr/local/bin/pinentry. If for some reason you
can't use that, you may put a line
Note that pinentry does not have any i18n features. The labels for all buttons
as weel as the prompts are provided by the caller. The Cancel you see are
merely fallbacks.
This is not a pinentry problem but one of gpg-agent. What version of gpg-agent
are you using?
Sep 15 2010
That is a problem of your scanner software.
Sep 8 2010
Sep 3 2010
Aug 25 2010
Aug 24 2010
It is unofficial and the FAQ is outdated anyway.
No, it is an error. See option --preserve-permissions.
Aug 21 2010
Aug 20 2010
Aug 19 2010
I fixed that in the README files but won't change it all over the project tree.
Fixed in trunk svn - comes also with info on the default pinentry.
This is a bug tracker and not a felp line. Please ask on a mailink list.
Aug 12 2010
Aug 11 2010
Jul 31 2010
Jul 30 2010
Compiling libassuan SVN revision 378 gives:
Jul 25 2010
Any news?
Jul 21 2010
Jul 20 2010
EDIT: The NO_SECKEY comes from a second key for which I do not have the private
key. But all I get after pressing cancel is BAD_PASSPHRASE, which could happen
as well if the user really got it right on the second try.
Hmmm... I am talking about GnuPG 1.4.10 here. I am not getting anything like
this. I am, however, using gpg-agent from gpg2.
What about this:
Solved problem, please close.
Jul 19 2010
Mailing List?, Ok.
ok, done