On Mon, 2018-01-22 at 22:07 +0100, Tino Mettler wrote: > On Wed, Jan 17, 2018 at 10:51:56 +0100, Patrick Ohly wrote: > > Yes, that's it: https://developer.gnome.org/libsoup/stable/libsoup- > > sess > > ion-porting.html mentions that the default has changed. > > > > So this might work: > > > > > > // use CA certificates if available and needed, > > // otherwise let soup use system default certificates > > if (m_verifySSL) { > > if (!m_cacerts.empty()) { > > g_object_set(m_session.get(), SOUP_SESSION_SSL_CA_FILE, > > m_cacerts.c_str(), NULL); > > } > > } else { > > // Checking enabled by default, disable it. > > g_object_set(m_session.get(), SOUP_SESSION_SSL_STRICT, > > false, > > NULL); > > } > > Hi, > > it worked for me. I included this patch in the 1.5.3 package that I > intend to upload this week.
Thanks for testing. I'll do a 1.5.4 with the same fix, but better don't wait for it. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
