I changed the suggestion to read:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 23 2019
The agent is an important part of gnupg and it does not make sense to single out cases when it might not be needed. I can't see any harm from having an agent running. In fact, one of th netxt versions will add yet another daemon which will then be needed in all cases.
Aug 22 2019
Thanks, @gniibe. From reading this patch (i haven't tested it), it looks like it would avoid most unnecessary agent launches (and agent communication) in the (b) case, which is a win over the status quo.
With me it happens all the time: Outlook 2013 x64 is half-maximized at
right border, and GPG asks for the passphrase on sending a mail from the
inline editor, on Windows 7 x64, then it always happens.
Thanks.
If it makes sense to warn a user for someone's preference when keys are imported,
here is a patch:
Aug 21 2019
i've just pushed rGc4b9eba1d6a63b73238dcbb644b365dc53563f3d to the dkg-fix-T4682 branch resolve this.
@dkg, I changed the title and adjusted the description to more accurately describe the situation.
Aug 20 2019
It was fixed in GnuPG master by rGc395f8315362: agent: Terminate pinentry process gracefully, by watching socket. and rG374a0775546b: agent: Close a dialog cleanly when gpg/ssh is killed for CONFIRM..
Those will be in GnuPG 2.3.
@skeeto can you edit the summary/title of this ticket to better reflect what you think the underlying issue is?
This appears to be https://bugs.debian.org/850946 and it does not appear to be fixed to me.
Aug 13 2019
Fixing t-lock is indeed a better solution however having an option to disable tests could be used in another context than fixing this issue.
For example, in the context of buildroot (which goal is to build a custom embedded linux system), this option could be used to save time during compilation as well as to save space on the embedded system.
Thanks for your report.
I think that adding an option for disabling tests is too much.
If it were AC_SUBST, we could use HAVE_PTHREAD in tests/Makefile.am.
In the current situation, just modifining t-lock is easier.
I think that I located the cause of this bug:
Those changes make the script work for me, specifically passing the input as an argument and not through standard input. Digging more, it looks like the underlying issue is related to using pinentry-tty (my case) or pinentry-curses when passing the OpenPGP input via standard input. This causes pinentry to give up before prompting. For pinentry-tty it fails with "ERR 83886340 Invalid IPC response" and pinentty-curses fails with "ERR 83918950 Inappropriate ioctl for device".
For my environment (Debian buster's 2.2.12 and another one from GnuPG master), both (no argument and foo) work well.
The invocation with argument let pinentry pop up to ask passphrase.
Aug 12 2019
Considering that early interop testing, you're probably right that this is a bug in the spec, not GnuPG. Otherwise this would have been pretty obvious long ago. The wording in RFC4880bis hasn't been corrected to match practice, so I should probably report this issue there.
Re-reading the original report from 2001 it seems that PGP and PGP do the same. Back then these were the only OpenPGP implementations (except for that book with the OpenPGP tool based implementation). We did quite some interop testing in the early years by passing OpenPGP data back and forth. So one could assume this is a bug in the specs becuase the specs are for large parts derived from the PGP 5 code base.
Aug 10 2019
Problem no longer exists. It has solved itself in the meantime. In addition, I ask for deletion of this account via the responsible administrator.
Are you seeing mixed-up MIME parts? or a different problem?
Aug 9 2019
No problem, I'm glad i could help, accented letters are always a pain between encoding.
Thanks for reporting.
Please explain in more detail what does not work. Outlook 365 is actually part of our test environment.
Aug 8 2019
/hex is just a diagnostic helper and not expected to be used to retrieve data.
Aug 6 2019
Aug 5 2019
Re-examining this now, I'm noticing the problem is not at all that it's being treated as signed, but that GnuPG is internally using a 32-bit unsigned integer for the time even though the key expiration scheme allows for expiration dates beyond 2106. Seeing dates in the past threw me off, and when I had originally tried using a zero creation time to test a broader range I ran into T4670.
I'm using Debian 10 "Buster" on x86-64, but for this ticket I used my own build of GnuPG so that I could demonstrate with the latest version. The system's GnuPG 2.2.12 has the same behaviors I showed here.
What OS are you using?
Aug 3 2019
I also observe that the text in the GUI prompts is remarkably unclear on its own. setting aside the grammar, punctuation, and wording, the prompts don't expose the usage flags set for the secret keys, which is possibly the only detail that a user with a single OpenPGP certificate would care about: "am i deleting my signing-capable subkey or my decryption-capable subkey?"
I was able to avoid reported behaviour; then n not a bug.
Aug 2 2019
Jul 31 2019
Please update the documentation for the function in that case.
Please see my explanation on gnupg-devel about why the trailing NUL is a source of pain and difficulty for would-be adopters.
Right, master will be 2.3.
No, it was not in mind. I introduced this only for backward compatibility. It will be extended iff we have a need for it.
Appending a nul byte is fail-safe programming and helps in debugging. It is on purpose and shall not be removed.
Jul 30 2019
My understanding is: it was introduced by rG370f841a0135: Enhanced last patch. in 2009 to give information to client (for a specific command at that time), possibly in a hope that server side would support the feature for all commands (and client could benefits).
Jul 29 2019
I think the problem is the following:
Jul 28 2019
False alarm. Turns out pinentry-gtk-2.exe is also not working all the time.
@bb - I've tried this, this doesn't appear to work. It looks like the Gtk2 pinentry doesn't grab focus when doing authentication, either. Interestingly enough, it also doesn't show in the taskbar.
Jul 27 2019
Note:
I added:
pinentry-program "C:\Program Files (x86)\Gpg4win\bin\pinentry-gtk-2.exe"
as a workaround to my gpg-agent.conf. This pinentry is able to grab the focus.
The card was replaced by the vendor. It seems to be a problem with the specific card. All other cards so far worked well. The issue can be closed.
Does anyone has an update on this issue?
I've just uploaded pinentry 1.1.0-3 to debian unstable with this fix in it.
@aheinecke thanks for the heads-up. i'll pull this in.
Jul 26 2019
Thanks. So, this is a positive report for 8E60:34C2. I'm going to add this VID:PID to support pinpad input by the internal CCID driver.
Pinpad input is not supported for Gemalto Ezio Shield, currently. OpenPGP card expects variable length pinpad input, and we don't have any positive report with the card reader.
we won't backport it to 2.2
Can you help me please to understand why you think that this is a regular use case?
Fairly typical situation: user needs to encrypt binary and text regularly
Pinpad input is not supported for Gemalto Ezio Shield, currently. OpenPGP card expects variable length pinpad input, and we don't have any positive report with the card reader.
@aheinecke , Would you consider re-opening this ticket?
Jul 25 2019
Wow, thanks for the quick response! I've applied your patch to the Ubuntu package (2.2.4-1ubuntu1.2), and gpg --card-status now works fine:
Thanks!
I can confirm that the patch from the referenced commit fixes the issue. Thanks for the quick action!
thanks for the report. I've commited a different fix 0e2e53c8987d6f236aaef515eb005e8e86397fbc which also should solve the problem.
Adding the patch here.