This was a very clear crash that is fixed now. Length was > 76 characters. This caused an improper realloc.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jul 9 2018
I noticed while looking at Netkey V15 (that signature card) support that we actually didn't have Netkey v2 in the whitelist for supported cards anymore since at least gpg4win 3.0. So I've updated this list accordingly.
Jul 6 2018
Jul 5 2018
Ok yeah. I can aim for a Gpg4win for next week, too.
What is the ETA for 2.2.9?
Finally changed it. Especially for keyserver search this was important.
IMO this can be closed. At least the problem for which I intended this ticket is fixed.
I agree that the underlying problem is something else but I also think that if a function can avoid a crash on bad input it should try to do so (or at least assert).
I'm going for Wontfix here. It's just too verbose and I don't really see the point of that additional information.
Jul 4 2018
Well I'm pretty sure the reason is that valuetable_buffer is not inialized in _gpgrt_estream_format. But the resulting behavior confused me. It would not crash. But it would also not print "gpg: Entschlüsselung als fehlgeschlagen angesehen: (null)" It would just print nothing instead of that string.
Got it. The reason was a broken translation. I've opened T4054 to fix in general that broken translations can cause crashes.
I can reproduce it with a german windows
Thank you for your detailed report!
changing to testing is our marker for "done in code but not fully tested / released". It helps to keep an overview of the issues which are "done" for the next release.
We have two cases:
- No MDC with a "modern" cipher algo
This is implemented now and can be turned of in the new config dialog.
ASCII Armored CMS files now also use p7m and p7s this is already handled gracefully by Kleopatra and does not require us to register new filetypes.
Jul 3 2018
I find this better then a new "KEYLIST_MODE_WKD" as it is more flexible and this flexibility with context flags is currently our thing anyway.
I don't think that this was ever working the Outlook 2007 code has been pretty much unchanged since 2013.
According to T1137 a workaround seems to be to enable the S/MIME Support in GpgOL.
Outlook 2007 is no longer supported. Neither by Microsoft nor by GpgOL. Sorry for that. But the 2010 and later GpgOL had a completely different codebase and we had to remove the support at some point.
Jul 2 2018
Maybe a first step would be a "KEYLIST_MODE_WKD" which sets "auto-key-locate clear,nodefault,wkd" (Would be nice for T3910 ) or just a ctx_flag "auto-key-locate" so that the caller can decide?
I'm pretty sure that the running command ist the reloadkeyscommand.
