This looks duplicate of https://dev.gnupg.org/T4317
Thanks for the report. underscore followed by an uppercase letter is actually reserved for the system; thus we should not have used that.
Sat, Mar 23
i don't think we need another column without the domain, i agree that it's easy enough to strip.
Great. Let me know when the newest gpg4win is released.
That keeps the interface the same just in case we ever change the format. It has also the advantage that you can use the tool to extract the mail address from the user id and thus see whether it is valid.
That seems plausible to me. I'm not sure why you'd include the @domain part in the output, since it's all strictly about the localpart. what happens if you provide some upper-case inputs?
fwiw, a comment over on T4422 contains a bash script that tries to force GnuPG to do its certificate/signature re-ordering. this doesn't produce anything canonical yet, but it's the closest i've come so far to getting GnuPG to do something repeatable with a certificate after merging (but even that is not quite stable).
(fwiw, all of this testing is done with GnuPG 2.2.14-1, using the package that is in debian/experimental right now; i'd welcome any corroboration with other versions)
as i experiment with this, i find an even weirder result with certificate re-ordering: the function above is not idempotent.
Here is a horrible bash function for doing the kind of stripping and re-importing that *does* cause signature re-ordering:
Fri, Mar 22
Hi - that did the trick. The linked gpgol.dll loads without any issues. However the decryption of e-Mails don't work. I get the
"OpenPGP Encrypted message (decryption not possible) Could not decrypt the data: Unsupported protocol" error.
Yeah, that worked halfways. Meaning, if I try to send the forwarded mail
from inline / reader / docked mode, the Button lights up but no sending
happens. If I send it from undocked window, it works and the original
problem doesn't happen.
So what about this:
With gcc-9 in Debian experimental, everything goes well.
Yes, the use of pragma is questionable, but let's see.
I think that a small tool or feature for gpg-wks-client would be better than extending the --with-colons format. A --dry-run option for example could list the filenames which would be created.
Thu, Mar 21
for a first patch to implement this.
Wed, Mar 20
Great. Thank you.
Thanks for the confirmation. Although I still don't really know how to fix it :-(
We are aiming for this week.
When will the new gnupg program be released so I can install it?
I can also confirm this bug!
There are reasons why we sometimes don't consult the return code. That is even declared in the code with a cast to void. Further we use gpg_error_t and int interchangeable under the assumption that an unsigned int and an int value have the same bit pattern.
Maybe we should get rid of the _Pragma operator in particular because it is not used often and we cond on compiler type later anyway.
Will you be so kind and look into this?
Applied to master. This is not suitable for 1.8
BTW, for looking at such hexdumps I use this little tool:
for whatever reason, i don't seem to be able to push to the branch on playfair, so i've also pushed the same commit over at https://gitlab.com/dkg/libgcrypt
Tue, Mar 19
Also might I add, this used to work perfectly fine in gnupg14. It seems that somewhere along the line a regression was introduced that is causing this erroneous non-compliant behavior in the HTTP client.
Why? Your explanation is invalid because it implicates dirmngr's HTTP client as not comforming to the spec laid out by the RFC. I've quite clearly explained--and backed up with the spec itself--that when a proxy variable is configured, a client should not be doing DNS lookup of the destination hostname. Is there something about that you are not understanding?
So where can I get the corrected file to install? I suppose I need the
new gpg4win, it hasn't been updated yet. If I need the signature or TAR
from your website how can I implement that?
@dkg If you propose a patch here I'm pretty sure that we will accept it. As one of our Python binding users you know better then us how the API should behave.
This is very strange, common to all the crashes in the log is that they happen while a keylisting is running and before the first key from that keylisting is returned. But this could be a red herring because the keylisting is always started immediately in a background thread and so it would be normal that if the crash occurs immediately that it would still be running. The keylisting code is extremely similar to Kleopatra though. So I don't understand why Kleopatra would then work for you.
News for 2.2.14, released 2019-03-19: