It's fixed in master by T3465: --pinentry-mode loopback with --delete-secret-keys, with new confirmation interaction.
For 2.2, you can use --batch and --yes, see T4667: "gpg: deleting secret key failed: No pinentry" when in --batch mode with --pinentry=loopback.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 10 2020
Nov 9 2020
The "Reliability History" says (in Chinese):
异常代码: c0000005 异常偏移: 0002b6c0
The error code c0000005 is something like SEGV on POSIX, I guess.
It occurred at the address 0002b6c0.
Oct 28 2020
Thanks for the info and my apologies for the regression. Please see my comment on T5045.
Oct 27 2020
I am facing a really similar problem currently in version 3.1.13 (on windows 10)
Although the self-test shows all checks passed. I found out that there is an issue with the cache dir file not being created/loaded.
See:
Oct 21 2020
All right, using the current master a Windows user with a Unicode name (e.g. Ⓐlfred E. Neumann) is now able to use gpg properly. Quite a lot of changes were required and backported to 2.2 will also be some work. More testing is of course required. Note that libassuan needs to be taken from Git until we have done a new release.
Oct 19 2020
Oct 18 2020
Oct 16 2020
@werner , if you would like some help moderating this bug tracker, I don't mind volunteering to do it.
Oct 14 2020
Please understand that this is a bug tracker and not a support line.
Oct 7 2020
Thanks for the quick analysis.
Oct 6 2020
We understand the problem, it's a regression from August. For T4083 we changed an internal function to better work with Windows UTF-16 filenames in preperation to at some point fully support UTF-16 and only use the wide character functions as system calls.
But that broke places where internally the local 8 bit encoding was still used.
I can reproduce this.
Observation:
The umlaut is displayed incorrectly on the command line (cmd.app) when the keybox file is created.
(This may or may not be relevant.)
Hi Zetrick,
Hi Zetrick,
Oct 4 2020
Hi all, I have this issue in Win10 in correct installation. Si I am interested what can I do to repair this issue. GPG is working correctly, but Kleopatra's selfcheck show this issue. Thanks. Portug
That is a version of gpg4win which we don't support or even know about. Please ask at their support site. Sorry.
Oct 3 2020
The name field is marked as optional but it is mandatory. This should be fixed.
Oct 1 2020
Version 2 is a bit too unspecific. Which version of what software are you using. Which OS?
Sep 30 2020
Hi,
I corrected all the accents. I created a PR here https://github.com/gpg/gpg4win/pull/3
Any ideas? Is there any other info needed that could help move this along?
Sep 26 2020
That code in gnupg has not been touched in a very long time so this may be caused by some side effect.
Sep 25 2020
Sep 20 2020
I tried using the portable version it wasnt portable apps, i used it the zip file option from this site, https://portapps.io/app/gnupg-portable/
Sep 17 2020
Last report more than two years ago.
Sep 9 2020
There are two problems that might be mixed in here:
What I noticed sometimes is that pinentry-qt properly becomes the ForegroundWindow but the input focus is not set on the line, even though an active cursor is shown in the line.
This might be a pinentry-qt specific issue and I look into that.
I have run the DbgView test twice, I don't know if there is the data you need.
Sep 8 2020
thanks for the report. Between Gpg4win-3.1.12 and Gpg4win-3.1.11 KF5ConfigWidgets was indeed updated so your report might point to a regression in that library.
Sep 7 2020
Sep 4 2020
Sep 3 2020
You need to get you toolchain correctly installed.
Thanks for your reply, but it is an OPTIONAL feature. The annoying part is not deleting the files. Comparing hundreds of time stamps to ensure you are current on what you want encrypted vs. unencrypted files that are either under development and/or complete, and therefore ready for encryption. This frequently needed comparison takes a significant amount of time, and is prone to error. Any responsible user will ensure there are tested file backups to prevent catastrophic losses, or they can simply NOT use the option.
Sep 2 2020
See also: T3506
I have removed that feature intentionally. There were some issues where encryption errors were not properly reported to Kleopatra and handled by Kleopatra. This could result in catastrophic data loss. I have fixed ~3 issues regarding to that and then decided that in our architecture we cannot absolutely guarantee that this never can happen and cannot happen in the future. We have resolved all the issues, but they could occur again.
Aug 27 2020
Aug 24 2020
What is the current encoding? OEMCP ?
So if gnupg version >= 2.2.22 Kleopatra needs to convert the passed filenames to UTF-8 and pass them with the --utf8-strings option to gpgtar. This needs to be changed in Kleo. -> Assigned to me.
Aug 22 2020
Done for master and 2.2.22 - libgpg-error 1.39 (not yet released) is required for the actual fix.
Aug 14 2020
Fixed.
Aug 13 2020
Taking: Still does not work although now --quick-set-expire is used by gpgme.
Thanks a lot.
Aug 12 2020
The expiry of the subkeys (and that of the primary key) can now be changed via a context menu action in the subkeyswidget.
Aug 8 2020
Thank you, Andre. Just updated here, problem fixed.
Aug 7 2020
Thanks Andre,
Aug 6 2020
To be honest I have not tried that but it should work because then it has another 50 tries to find a name like "attachment_51.txt" because we stay in the loop.
I think this is good now.
I'm not sure what to do with the issue. For further analysis we would need to figure out what third party software breaks the MIME structure of the mail. That is more something for a support contract and not for the general issue tracker. This issue is very specific to your setup and so I'm not surprised that Microsoft says it can't help.
Thanks. rMdb82e99 resolved this.
We have released 3.1.12 which updated all the GUI libraries Kleopatra uses and I got some feedback in related issues like T4689 that this might have helped.
@bzbue1 Thanks for the info.
I can no longer reproduce this in Gpg4win-3.1.12.
Aug 4 2020
Jul 31 2020
Iyou look at the key on the command line (or with Kleopatra's certificate manager), for example by using "gpg --list-key foo@bar.com" or by applying the command "gpg --show-keys" on the pasted keyblock you get this:
Jul 30 2020
Something looks odd about the way I pasted that key in there. The last 4 characters are bold, and it is missing an = sign.
Jul 29 2020
to give you any help I would need to know the exact error. I can only tell you that this is not a problem related to Gpg4win something else must be messy on your system. The Uninstaller of Gpg4win cleans up all registry keys that do not contain user config and all files should be removed unless some other process on the system interferes.
Jul 28 2020
Jul 27 2020
Phabricator allows it again to upload patches. It's D507
In Kleopatra/src/dialogs/subkeyswidget.cpp there is already a context menu for subkeys.
Still an issue, just noticed that with the 3.1.12 release announcement, it really looks ugly.
Jul 20 2020
Dear gnupg developers.
I have contacted the Microsoft to get their analysis as well.
A Case #:20812681 has been registered. Where Microsoft stated that third party developers of plugins like GpgOL have their channels and should contact Microsoft directly in cases like this. Further analysis has been denied to me.
Jul 19 2020
- - it get stuck with empty window
Jul 18 2020
I started "gpgconf --launch gpg-agent" and afterwards PuTTY. Then I am asked to "login as:". After entering the username, the error "PuTTY Fatal Error: No supported authentication methods available (server sent: publickey)" occurred.
Jul 17 2020
iirc, you need to start gpg-agent before you use putty; thus do a "gpg -K" or "gpgconf --launch gpg-agent".