- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 28 2018
Mar 27 2018
Was reported to me again in the context of paperkey export / print secret key in Kleopatra.
Got it. This was a bug that was around for ages but only started to occur in the verificationresult when we started in 3.0 to show the KeyID / Options for the unknown certificates.
In my opinion we should assume that c:/ was meant.
Mar 26 2018
rO4c5eed308829 fixes this.
Again, thanks for your time testing it again.
Thanks for trying out the beta and your report.
Basic support is in. Maybe we should open a task on how to improve it.
It's two bugs working hand in hand here.
This was fixed. The check for VS-NfD mode was crashing.
Thanks a lot!
The log shows pretty much whats going wrong. I've opened T3863 for this to have a clear issue for the problem.
Mar 23 2018
Playing around with this a bit: I can get messages to pass if I set the content type of our MOSS attachment to multipart/encrypted .
The problematic thing there is that there is a comment in the code that explicitly states that multipart/signed is needed to activate MSOXSMIME. So we have to be careful, maybe even check the Server Version somehow as I don't want to break older stuff.
Thanks for your report. Sadly I cannot reproduce this, I went back in my archives and even mails from 2015 / touched by Gpg4win 2.x work without a problem.
Thanks. After seeing this report I ran a spellchecker on the translation and found some more typos ;-) Will be fixed in the next version.
This should no longer happen with Gpg4win-3.1.0 as GpgOL now uses gnupg's --locate-key mechanism to find a matching key.
In T3769#111899, @hs wrote:Behavior is the same as 3.0.3 /3.1.0beta32.
It reads encrypted e-mails if Titus plugin is disables (GpgOL as the only plugin).
Mar 22 2018
Could you please test again with the beta38 (or later) from https://www.gpg4win.org/version3.1-de.html It contains the change now.
I'm closing this as I've got confirmation that one crash was fixed by disabling async encryption again. And a class of general "Crash when encrypting" bugs that were related to the communication between Kleopatra and GpgOL no longer exists as Kleopatra is no longer used when encrypting from GpgOL in gpg4win 3.1.0.
Thanks for your report. This has been fixed for the next version ( https://bugs.kde.org/show_bug.cgi?id=391222 )
Mar 21 2018
Thanks for testing and the confirmation / praise ;-)
The second user ID in my test case was an "URL". So we now use what ever the "raw" user id data is as the Name if both name and email are empty.
I don't find an easy way to fix this.
Did not really help. It does not work for English somehow and even with a different language like french very few additional buttons were translated. Still a weird mix.
I just tested changing passphrases and indeed this is very ugly. Especially as this opens up a wide range of error states where you have different passphrases for different subkeys etc.
I'm not 100% certain but I think that it is likely that your problem is fixed with the upcoming 3.1 version. We have reworked how GpgOL encrypts there a bit ( T3509 )