Hello,

I just wanted to let you know that the new code is now available [1, 2].

The TLS/SSL support has been reworked. Basically, the server core has  
been cleaned of any reference to the OpenSSL or GnuTLS. The crypto  
support has been moved to a new plug-in type, and all the OpenSSL  
related code has been re-implemented within of of these new plug-ins.

That means:
- Now the Cherokee's core is smaller and cleaner
- GnuTLS support has been discontinued. The door is open for anyone to  
write a GnuTLS based plugin, though.
- The libcherokee library does no longer depend on a SSL library  
(which might have an effect on the distribution packages. That is up  
to the packagers, actually).
- The change was been quite big. Testing is really appreciated.

Cheers!!


  1.- http://www.cherokee-project.com/download/trunk/
  2.- http://www.cherokee-project.com/svn.html

On 14-nov-08, at 20:50, Alvaro Lopez Ortega wrote:

> Hi there guys!
>
> Cherokee currently support the two most spread TLS/SSL libraries:  
> OpenSSL and GNUTLS.
>
> There isn't a clean reason for supporting both of them, actually. At  
> the beginning it was kind of interesting to support the two  
> different libraries, but nowadays I think it's much more important  
> for the project to be maintainable than feature redundant.
>
> That's the reason I'm sending this mail. I've been thinking lately  
> about dropping the GNUTLS support from Cherokee, and I'd to know  
> what you guys think of that. Would it impact you?
>
> At the end of the day OpenSSL (libssl) is a de-facto standard  
> nowadays, so even though we would lose some bizarre functionality  
> (such as be able to use OpenPGP certificates instead of X509 certs),  
> I think it would be a change for the best.
>
> So, what do you think? Speak now or forever hold your peace ;)
>
> --
> Greetings, alo
> http://www.alobbs.com/
>

--
Octality
http://www.octality.com/

_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee

Reply via email to