a GUI for GNU PG among other things
Thu, Jan 16
Mon, Jan 13
Dec 23 2019
The Name field in GnuPG needs to be at least 5 _bytes_ long. Given that UTF-8 is required for Hangul, a 3 _character_ name is at least 6 bytes long and thus passes gpg check. The Name field is also optional and the whole test can be skipped using --allow-freeform-uid.
Dec 19 2019
This is fixed in Gpg4win-3.1.11
Dec 16 2019
Thanks for the report.
Will be released with 3.1.11
This is done in 3.1.11
Dec 12 2019
Nov 14 2019
Nov 12 2019
Nov 7 2019
Without --expert my proposal for full-gen-key would be:
Nov 4 2019
Nov 1 2019
Maybe it is the same issue described in https://dev.gnupg.org/T4717 ?
Oct 31 2019
Oct 30 2019
Oct 29 2019
Oct 3 2019
Sep 23 2019
Sep 12 2019
This is generally the better tracker to report Gpg4win / Kleopatra issues. The git systems are linked in a way that I can both automatically add a commit here and in the KDE tracker.
I just noticed the KDE report a bit quicker because there is less traffic, but I would have seen it here within the day.
Sep 9 2019
I give this normal priority even if it is a whish because I have the same whish and already have some code around that would make it more comfortable, especially if it is used directly in GpgOL.
Aug 30 2019
Strange. Can you please go to the command line (cmd.exe) and run gpg --verify "c:\<path to>\gpg4win-3.1.10.exe.sig" "c:\<path to>\gpg4win-3.1.10.exe.sig"
Jul 24 2019
Jul 23 2019
This pretty much matches my test setup. As the crash is in GPGME it is out of Kleopatra's hand. So I'll try to write a test that repeats such a signing for lots of times. I think this is probably some random race condition.
I don't think I can reproduce it, at least it didn't happen anymore after restarting and continuing the imports. AFAIR it happened after importing the "Master Key", during trying to import the "Release Key" from https://www.chiark.greenend.org.uk/~sgtatham/putty/keys.html
Ah and maybe one more hint: I have several keypairs, so the dialog for choosing the keypair to be used appears in the next step.
Jul 2 2019
Kleopatra was already using this keyserver at the time i took the screenshots, which is why i opened the ticket since it was working in the command line.
Jul 1 2019
I have no idea – I’m not familiar with cmd.exe – Do you have step by step instructions on how to do this?
Digital Marketing Manager
Mainline Tel: +44 (0)1895 813 000
Fax: +44 (0)1895 200 541
All Pet Solutions Ltd is a company registered in England and Wales.
Unit 203| Riverside Way | Uxbridge| UB8 2YF
Please consider the environment before printing this e-mail.
This email, including attachments may be privileged, confidential and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you have received this email in error please notify the sender and delete it from your system. Emails are not secure and may contain viruses. No liability can be accepted for viruses that might be transferred by this email or any attachment.
All Pet Solutions Ltd. Registered office: 22 Wycombe End, Beaconsfield, Buckinghamshire, England, HP9 1NB. Registered in England and Wales. Registered No. 05678076
From: aheinecke (Andre Heinecke) <firstname.lastname@example.org>
Sent: 01 July 2019 07:44
To: Chris Baillon <Chris.Baillon@allpondsolutions.co.uk>
Subject: [Task] [Claimed] T4581: Kleopatra stuck in loading the certificate cache
aheinecke triaged this task as "Normal" priority.
aheinecke claimed this task.
aheinecke added a comment.
can you please open the console (cmd.exe) and do a "gpg -K" and "gpgsm -K"
do these commands list all your secret keys or do they hang?
Also please try killing the process "gpg-agent.exe" through the Task manager and try to open Kleopatra again.
Cc: aheinecke, allpond, Neurone, Rafixmod, Fox, ccharabaruk, gp_ast
This is an automated email from the GnuPG development hub. If you have registered in the past at https://bugs.gnupg.org/ your account was migrated automatically. You can visit https://dev.gnupg.org/ to set a new password and update your email preferences.