Free-Busy via https

[Sandro Knauß]

Hey,

This bug is known as bug 2862 (and fixed):

https://issues.kolab.org/show_bug.cgi?id=2862

But it is only fixed in master libcaledering. The other way is to use the 
mewest kdepimlibs 4.13.2.

> Do I have to have a signed certificate for this to work?

Nope. The errors about the unchecked ssl are only warnings, so it connects to 
the server also with untrusted certificate.

Regards,

Sandro

Am Mittwoch, 18. Juni 2014, 20:01:17 schrieb Janszen, Josh:
> All,
> 
> I am trying to get Kolab free-busy working via https:// but nothing
> seems to be working, I tried via http:// also and it doesn't seem to
> work either. When looking through the logs it shows;
> 
> kolab-freebusyd(22369) KIMAP::SessionThread::reconnect:
> connectToHostEncrypted "localhost" 993
> (19:45:04) findkolabfoldersjob.cpp(111):        "GetMetaData failed,
> server replied: A000011 BAD Missing arguments $
> kolab-freebusyd(22369) KTcpSocket::showSslErrors: "The host name did not
> match any of the valid hosts for this cert$
> kolab-freebusyd(22369) KTcpSocket::showSslErrors: "The certificate is
> self-signed, and untrusted"

-- 
Sandro Knauß
Software Developer

Kolab Systems AG
Zürich, Switzerland

e: knauss at kolabsys.com
t: +41 43 501 66 91
w: http://kolabsys.com

pgp: CE81539E Sandro Knauß
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/users/attachments/20140619/9421d25e/attachment.sig>