Re: [Evolution-hackers] evolution-kolab: Camel.HttpStream in the wild (?)

2010-08-06 Thread Christian Hilberg
Hi there, On Thursday 05 August 2010 Matthew Barnes wrote: On Thu, 2010-08-05 at 18:30 +0200, Christian Hilberg wrote: Result: While libsoup should build against the current GnuTLS lib (development version, 2.11.0), which has PKCS #11 support since a few weeks now, libsoup has no

Re: [Evolution-hackers] evolution-kolab: Camel.HttpStream in the wild (?)

2010-08-06 Thread Christian Hilberg
Hi Stef, On Friday 06 August 2010 Stef Walter wrote: [...] FWIW, gnutls is working on PKCS#11 support. The first bits have been added and I've been working with the gnutls maintainers on some of the remaining parts. I believe libsoup will start using this in the near future. Yes, we've seen

Re: [Evolution-hackers] evolution-kolab: Camel.HttpStream in the wild (?)

2010-08-05 Thread Christian Hilberg
Hi again, On Wednesday 04 August 2010 Christian Hilberg wrote: On Wednesday, 04 August 2010, Matthew Barnes wrote: On Wed, 2010-08-04 at 16:03 +0200, Christian Hilberg wrote: Is there any good alternative to using libsoup which makes use of NSS? We're pretty much depending on the

Re: [Evolution-hackers] evolution-kolab: Camel.HttpStream in the wild (?)

2010-08-05 Thread Matthew Barnes
On Thu, 2010-08-05 at 18:30 +0200, Christian Hilberg wrote: Result: While libsoup should build against the current GnuTLS lib (development version, 2.11.0), which has PKCS #11 support since a few weeks now, libsoup has no infrastructure for handling client certificates at all [1] and GnuTLS

Re: [Evolution-hackers] evolution-kolab: Camel.HttpStream in the wild (?)

2010-08-04 Thread Matthew Barnes
On Wed, 2010-08-04 at 12:50 +0200, Christian Hilberg wrote: Using the Camel.HttpStream should do the trick - is that correct? I've seen the Camel.HttpStream being used within Anjal (file em-format-mail.c). Is this Camel HTTP part being used somewhere else as well (to be used as another

Re: [Evolution-hackers] evolution-kolab: Camel.HttpStream in the wild (?)

2010-08-04 Thread Christian Hilberg
Hi Matthew, thanks for the prompt reply. On Wednesday, 04 August 2010 Matthew Barnes wrote: On Wed, 2010-08-04 at 12:50 +0200, Christian Hilberg wrote: Using the Camel.HttpStream should do the trick - is that correct? I've seen the Camel.HttpStream being used within Anjal (file

Re: [Evolution-hackers] evolution-kolab: Camel.HttpStream in the wild (?)

2010-08-04 Thread Matthew Barnes
On Wed, 2010-08-04 at 13:28 +0200, Christian Hilberg wrote: Does libsoup make use of NSS (just the newbie's uninitiated question)? It uses GnuTLS for transport layer security. http://www.gnu.org/software/gnutls/ Hey, thanks for that hint! :-) Maybe it would be wise to mark such classes as

Re: [Evolution-hackers] evolution-kolab: Camel.HttpStream in the wild (?)

2010-08-04 Thread Christian Hilberg
Hi there, On Wednesday 04 August 2010 Matthew Barnes wrote: On Wed, 2010-08-04 at 13:28 +0200, Christian Hilberg wrote: Does libsoup make use of NSS (just the newbie's uninitiated question)? It uses GnuTLS for transport layer security. http://www.gnu.org/software/gnutls/ Is there any good

Re: [Evolution-hackers] evolution-kolab: Camel.HttpStream in the wild (?)

2010-08-04 Thread Matthew Barnes
On Wed, 2010-08-04 at 16:03 +0200, Christian Hilberg wrote: Is there any good alternative to using libsoup which makes use of NSS? We're pretty much depending on the (mostly) working NSS infrastructure for PKCS #11 and token handling for certificate based client auth. That I don't know. You

Re: [Evolution-hackers] evolution-kolab: Camel.HttpStream in the wild (?)

2010-08-04 Thread Christian Hilberg
Hi Matthew, On Wednesday, 04 August 2010, Matthew Barnes wrote: On Wed, 2010-08-04 at 16:03 +0200, Christian Hilberg wrote: Is there any good alternative to using libsoup which makes use of NSS? We're pretty much depending on the (mostly) working NSS infrastructure for PKCS #11 and token