Hi!

I am the maintainer of jabberd14. In version 1.6.0 jabberd14 is completely available with the exception of snprintf.c file in the jabberd/lib directory which is taken from Apache and therefore licenced under their (IMO compatible) licence.

The only remaining problem why I could not release the software under GPL as the main licence is, that some people think, that using OpenSSL might not be compatible with the GPL. But in any case using jabberd14 without SSL/TLS support IS possible using the GPL - which is anyway an improvement over the latest packaged version of jabberd14 in Debian which is jabberd14 1.4.3.1.

The only place where this old version supports SSL/TLS is for accepting connections on port 5223. I could imagine that a package, that has problems using OpenSSL with the GPL licence, could build jabberd without any SSL/TLS support (therefore not linking against OpenSSL) and use a tool like stunnel to forward traffic from port 5223 to port 5222.

I am working on allowing to use GnuTLS instead of OpenSSL, but still have to solve some issues I have with using GnuTLS.

And one note I want to add:

jabberd 2.x is NOT a newer version of jabberd 1.4.x / jabberd14 1.6.0 as seems to be expected by a comment above. jabberd2 is a completely different implementation of a Jabber server, accidently just sharing the same name. Compared using the "official" feature score at http://www.jabber.org/software/servers.shtml jabberd14 1.6.0 does support more features than jabberd2 does.


Matthias

--
Matthias Wimmer      Fon +49-700 77 00 77 70
Züricher Str. 243    Fax +49-89 95 89 91 56
81476 München        http://ma.tthias.eu/


Reply via email to