- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Apr 5 2018
Apr 4 2018
In T3864#112250, @aheinecke wrote:
- Resetting the GnuPG Profile back to default in Kleopatra does not work.
I doubt that I will be able to fix this. The problem is that for Outlook we build the signed mail structure, which is a multipart MIME message. If you receive such a mail with a non crypto client you see the plain text and a pgp-signature attachment. That is why Outlook shows it as "attachment".
Normal prio as I don't think that this is a regression.
Thanks for trying out the beta. I was about to open an issue about this as someone in the forum reported the same thing. https://wald.intevation.org/forum/message.php?msg_id=5759
- Aborting the keyresolver results in error code 5 in GpgOL
- Resetting the GnuPG Profile back to default in Kleopatra does not work.
- Add uid in Kleopatra results in General Error.
Apr 3 2018
Mar 29 2018
fixed with rev. 4fbbd134b865b1203b1914eb1623fa65aab8cb75
I might have changed the caller (GpgME++) but what convinced me that the change in core is better is that op_keylist_next sets the return value to NULL on error.
Mar 28 2018
Apologies for not replying to your mail directly. I've marked it in my INBOX to do the test with 3.0.3 first but have not gotten around to it.
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.