Cool! Thanks for testing :-)
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 8 2018
I still don't have any clue what could be wrong here.
I can't reproduce this. I sent myself a Mail with capitalized "Andre.Heinecke@intevation.de" while my key only has an identity for "andre.heinecke@intevation.de" and it worked as expected:
Mh, that is strange and indeed a bug if that is so. GpgOL should do some simple normalisation which should prevent exactly such a problem. I'll look into it.
Question has been answered. Closing this.
Thanks for the hints.
The problem for us is that we want to rely on Debian Stable for building Gpg4win and there is only NSIS 2.51 in debian :-/ Maybe we make an exception and package NSIS 3 ourself for debian.
With 3.1 ( https://www.gpg4win.org/version3.1.html ) the problem should be gone. We still have to block outlook when the inline editor is used but that left no artifacts in the past. And if a Mail Window is opened we do not block outlook anymore. We only disable it to show a modal dialog.
At some point we really need to look at better error handling so that such an error would be more visible in the UI.
As this is easy to test and I tested it myself I think I can mark it as resolved.
Thanks for your help / report.
With Gpg4win 3.1.0 ( https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe ) GpgOL no longer uses Kleopatra for signing. So this problem can no longer exist.
I'm lowering the priority to Normal. I've done a lot of GpgOL work and Testing for the upcoming 3.1.0 release and have not seen this problem.
Leaving this open until we have a new version of GnuPG in the installer. While Kleopatra should no longer crash it won't properly work without the patch to GnuPG.
Got confirmation In Bugs.kde.org that this is fixed https://bugs.kde.org/show_bug.cgi?id=389792 as my tests also showed this -> resolved.
We have this now. There might be bugs but in general this works.
Mar 7 2018
A Beta of 3.1.0 is now available:
https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe
Should work with the current beta: https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe Although the window mangement is still a bit "iffy" but we at least switch back the focus.
Yes sorry, I decided against a release specially for that is it is not super critical, no data loss.
A beta of the next version where this is fixed is available now: https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe
I've uploaded a beta for the upcoming 3.1.0 Version: https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe
Version 3.1.0 now supports sign & encrypt and sign only for G Suite accounts as long as there are no attachments on the mail.
I wonder if this also works similar in a multi user system:
Mar 6 2018
From the log I can see that GpgOL picks up the wrong "Sender" address. It thinks that you sent the mail yourself and then the mail address <> signature does not match. So it is not flagged as Trusted.
When we detect GnuPG > Version 2.1.15 Kleopatra now offers (and has it as default for ECC) to use cv25519 / EdDSA
Thanks for the report. The broken sentence came from an unterminated hyperlink. I fixed the spelling and the link.
I've started adding a workaround, but shelved it for now. Any workaround would not work for plain signed mails and would not be interoperable with other clients.