- User Since
- Mar 27 2017, 4:48 PM (269 w, 1 d)
Please let us turn this into a fatal error again. I had too many support cases where Kleo was actually run with Admin rights and messed up the permissions. To help with development issues and for the sake of some blockheads introduce an envvar to bypass the error.
For me it is faster:
ntbltls does not implement compression:
Please remember that GnuPG is a Unix tool. You might be interested in GPGME to write your own frontend.
As a Unix tool GnuPG does not touch its output. Diagnostic messages are only filtered for ASCII control characters because that is what command line tools should do. Everything else is up to your terminal emulation.
Thanks. The solution should thus be easy.
Sun, May 22
This specificiation is a draft which has not even been discussed in the WG. In any case gpg won't implement this because it would break processing of existing data.
Sorry, no. Use cat(1) for such translations.
Fri, May 20
Thu, May 19
It seems that editing a pre-created revocation certificate on Windows with Notepad doesn't let Kleopatra detect this correctly as OpenPGP file and thus refuses to import. Works on the command line but needs more testing.
Wed, May 18
AFAICS, we need to implement a new Assuan flag and wipe the data passed to the callback after the callback returned.
That is expected. The export re-encrypts the secret parts to comply with the OpenPGP specs and this includes a salt andf IV and thus the output must be different.
Tue, May 17
Lets implement it for 2.3
Mon, May 16
Fri, May 13
We meanwhile released two versions to our clients and are looking on how we can make it available to the community.
We have everything ready for a GnuPG Desktop Appimage but we first need a business case to maintain it.
We have a workaround by using a recent version of gpgtar directly. Thus lowering priority.
Please disable all other Add-Ins as well as extra security tools running on that machine to see whether there is some interference with them.
But only with an option - in general showing expired keys is annoying. For revoked keys the situation is different in case of a compromise - but many users revoke old keys anyway and we don't make use of the revocation reason. If we would consider the latter the UI/Support would be more complicated than useful.
Thanks for opening a ticket.
Thanks. Should be applied.
I can imagine thar there are use cases for this. Thus I see no problems for the first part.
Wed, May 11
Please check the 2020 certificate by using the details dialog. Has it a valid encryption subkey?
it was noted that this also affects other ML hosted there like those of freie-software.org
Tue, May 10
Mon, May 9
Fri, May 6
No sure, you could also consider the is_cardkey flag to mean that a secret key might be available. FWIW, GPA sets it internal secret key flag based on the type of listing done; thus I see no problem if you want to change the behaviour.
Thu, May 5
Ours are even newer (5.4.3). Did you the Yubico tools to switch to curve443?
In any case, is it possible that you apply my fix and test again?
Your Yubikey's firmware version is 5.2.7 - let me see what versions we have in stock to test my fix.
When we implemented this first, Libgcrypt had no appropriate KDF support. I recall that I considered to change this but it turned out the for 2.2 the changes are too large. For 2.3 we will consider such a change.
Wed, May 4
I am not sure about the crash but the unknown curve is
188.8.131.52.4.1.115184.108.40.206 which seems to be a GNU OID for curve448
What I would do in this case is to stop the gnupg daemon amd anything whiuch might start them and run scdaemon under valgrind.
Tue, May 3
Mon, May 2
FWIW, the original idea with gpgscm was to provide code which does no rely on any gpg stuff so it can be merged back into upstream. I am not sure whether this still makes sense.
Fri, Apr 29
Thu, Apr 28
Please try a decent version of Gpg4win - we have fixed dozens of bugs in the mean time If the problems persists, please re-open this bug.
Conflicts between Add-Ins are often unavoidable. We have a list of known issues at:
If you have more information on that ESET thingy please enter it into the above wiki or leave some description here.