@gv: I am another user (not the developer), but here is a workaround I found. Type ctrl-D instead of ctrl-C to terminate pinentry-tty.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Dec 3 2019
I'm sorry, this issue is far from fixed.
Dec 2 2019
This is a support question. Please use one of the public support channels as listed at gnupg.org or ask for a quote at a commercial service (https://gnupg.org/service.html).
Dec 1 2019
Nov 30 2019
Nov 29 2019
I am currently investigating the issue known as CVE-2019-14855 for Debian's LTS version Debian 8 "Jessie" and even Debian 7 "Wheezy".
Regression due to a faulty backport. Fixed in repo; patch is F1052802
Thanks for reporting.
Okay, I can replicate that on gnupg 2.2; it works correct on master.
Nov 28 2019
I am not sure what you want you are going. I see is a verify command using an unknown file or number of files without knowing its content (using globbing (*-SOMETHING) is not a good idea). Some signature is verified okay but it is not known whether the key is trustworthy. You export a ke and then you do a verify on the key - this can't work because a key-file is not a signature.
Nov 27 2019
Sorry, a fix didn't made it into 2.2.18.
Nov 26 2019
This is actually unused code and it will never be called with ERR == 0. Will fix it in master anway.
No bug.
The LDAP code is actually in very bad shape because @neal added it without utilizing the ldap wrapper and thus a timeout won't work reliable.
See T4760.
[ Please do not post each compiler warning as a single report. That is just just too much overhead and we do see such messages ourselves if you would provide a bit more information. ]
Nov 25 2019
Unusable v6 interfaces are now detected on Windows and then not used.
To be clear, i believe @mgorny means that he wants the User ID containing the e-mail address to be considered *valid* (that is, full or ultimate validity). I don't think this operation should care about ownertrust.
Nov 24 2019
Nov 23 2019
The manual states that --standard-resolver is mostly for debugging. The reason you get an "not enabled" is that we can't allow direct DNS queries in Tor mode which would happen with the system (standard) DNS resolver.
In T4726#130765, @werner wrote:Given that the the angle brackets are elsewhere used to indicate a search by mail address, it would be okay to allow for them in this case too (that is dkg's second example).
[...]
To answer your question: With the exception of case two this is desired behaviour also in the future,