The problem was the CRL checking that is broken with no certificate revocation list in the certificate. The workaround is to disable CRL checking.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Aug 21 2015
Aug 20 2015
Importing the keys directly trusted the root certificate and imported it into the trustlist.txt.
smime on windows is also working once the "Never consult a CRL" option is activated in Kleopatra (which is the disable-crl-checks option in the config file). With that it's possible to select the certificate, and to encrypt/decrypt and sign a message.
The test just got stuck for me.
On windows various parts are not translated to german, including:
- KMail Configuration: The bar on the left is translated, but the title "Configure - KMail" and the contents of each "tab" is not translated.
- All the rest of the kmail interface is not translated (German is selected as application language).
Couldn't find any reliable way to trigger the problem
The innodb_force_recovery option doensn't seem to have any effect on this.
2015-08-20 12:39:19 1000 [Note] Plugin 'FEDERATED' is disabled.
2015-08-20 12:39:19 63c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-08-20 12:39:19 1000 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-20 12:39:19 1000 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-20 12:39:19 1000 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-08-20 12:39:19 1000 [Note] InnoDB: Memory barrier is not used
2015-08-20 12:39:19 1000 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-20 12:39:19 1000 [Note] InnoDB: Not using CPU crc32 instructions
2015-08-20 12:39:19 1000 [Note] InnoDB: Initializing buffer pool, size = 80.0M
2015-08-20 12:39:19 1000 [Note] InnoDB: Completed initialization of buffer pool
2015-08-20 12:39:19 1000 [ERROR] InnoDB: Cannot create log files because data files are corrupt or the database was not shut down cleanly after creating the data files.
2015-08-20 12:39:19 1000 [ERROR] Plugin 'InnoDB' init function returned error.
2015-08-20 12:39:19 1000 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2015-08-20 12:39:19 1000 [ERROR] Unknown/unsupported storage engine: innodb
2015-08-20 12:39:19 1000 [ERROR] Aborting
2015-08-20 12:39:19 1000 [Note] Plugin 'FEDERATED' is disabled.
2015-08-20 12:39:19 63c InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-08-20 12:39:19 1000 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-20 12:39:19 1000 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-20 12:39:19 1000 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-08-20 12:39:19 1000 [Note] InnoDB: Memory barrier is not used
2015-08-20 12:39:19 1000 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-20 12:39:19 1000 [Note] InnoDB: Not using CPU crc32 instructions
2015-08-20 12:39:19 1000 [Note] InnoDB: Initializing buffer pool, size = 80.0M
2015-08-20 12:39:19 1000 [Note] InnoDB: Completed initialization of buffer pool
2015-08-20 12:39:19 1000 [ERROR] InnoDB: Cannot create log files because data files are corrupt or the database was not shut down cleanly after creating the data files.
2015-08-20 12:39:19 1000 [ERROR] Plugin 'InnoDB' init function returned error.
2015-08-20 12:39:19 1000 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2015-08-20 12:39:19 1000 [ERROR] Unknown/unsupported storage engine: innodb
2015-08-20 12:39:19 1000 [ERROR] Aborting
With "disable-crl-checks" in .gnupg/gpgsm.conf I managed to use my self-signed certificate and encrypt/decrypt an email on linux.
disable-crl-checks is only necessary because the certificate I created has no crl list (crlDP: [none] in the dump)
What about the tests inside kdepim exspecially messageviewer/rendertest,this onetests smime and gpg encrypted/signed messages.
Aug 18 2015
Probably less important than smime support
I could trust my root certificate, but then not the subcertificates...
Zanshin translations are now correctly built after updating the translation files.
The problem was that the windows build takes a separate git repository as source for the translations. After copying the translations it works now as expected.
Submitted to libkolab-1.0
Low priority because we normally don't need to create new certificates.
Aug 17 2015
I guess we don't strictly need the capability to create new keys, as long as we can work with existing ones. Also, any idea whether this depends on a specific version or is universally broken?
I assume that means we can close this bug?
Which is probably the reason that the zanshin.gmo file is not generated.
Zanshin has no translations it seems:
The file was matched by one of the blacklist expressions, and inputfiles.nsh was not actually used.
Aug 14 2015
Value can't be converted to integer.
assuan_sendfd (ctx=0x0, fd=0x10) at assuan-buffer.c:518
518 if (! ctx->engine.sendfd)
gdb$ thread apply all bt
And with all of that working decryption in kmail works as well.
To decrypt something using gpg2:
Aug 13 2015
While the relevant file has now been included in input.nsi, it doesn't seem to get picked up by the installer...
Looks like a good idea. Gather input at the beginning and less guesswork all over the place. Nice =)
...and the problem was that kde-include-common.xsl was missing. What a brilliant fucking system.
This one works though:
meinproc4 --stylesheet "C:/Users/kolab/kderoot/share/apps/ksgmltools2/customization/kde-chunk.xsl" --stdout "C:/Program Files (x86)/Kontact E5/share/doc/HTML/en//kmail/index.docbook"
And with explicit stylesheet:
meinproc4 --stylesheet "C:/Program Files (x86)/Kontact E5/share/apps/ksgmltools2/customization/kde-chunk.xsl" --stdout "C:/Program Files (x86)/Kontact E5/share/doc/HTML/en//kmail/index.docbook"
Same testcase with meinproc:
meinproc4 --stdout "C:/Program Files (x86)/Kontact E5/share/doc/HTML/en//kmail/index.docbook"
This is the call that somehow fails in kdoctools/xslt.cpp:
Testcase: kioclient.exe cat help:/kmail/index.html
Aug 12 2015
All of this was tested using gpg4win-vanilla 2.2.0 which contains the same libassuan and gcrypt version as we use in emerge.
It was not possible to change the ownertrust using kleopatra.
Note that importing a gpg certificate from a server crashes on linux. Importing from a file works on windows and linux.
Aug 11 2015
Aug 10 2015
Seems to work now together with http://files.gpg4win.org/gpg4win-vanilla-2.2.0.exe
Note that we have hardcoded paths in the pgpme we bulid that point to the gnupg installation.
We decided to go with the installer:
http://files.gpg4win.org/gpg4win-vanilla-2.2.0.exe
After the fixes you can ship this.
Please add a comment here what's going on exactly and why this code is needed, it's not exactly self explanatory ;-)
whitespace
Aug 7 2015
The problem seems to be that the kio job to generate the help files is not started.
If I copy the cache files from .kde to .kontact the help opens just fine. Debugging kio seems to be next no impossible, while I can configure debug output going to a file with the uninstalled version, the installed version does not create the debug output file, nor give any indication why it isn't doing that.
Aug 6 2015
When starting khelpcenter from the install directory instead of the builddirectory, meinproc4.exe is not started according to processmonitor.
Aug 5 2015
Aug 4 2015
Aug 3 2015
Not reproducible