Hi, On Tue, 2008-06-10 at 21:18 +0200, Robert Millan wrote: > On Tue, Jun 10, 2008 at 11:50:47AM +0200, Miriam Ruiz wrote: > > 2008/6/10 Guus Sliepen <guus@debian.org>: > > > On Mon, Jun 09, 2008 at 11:43:53PM -0500, William Pitcock wrote: > > > > > >> * URL : http://www.ircd-charybdis.net > > >> * License : GPL > > >> > > >> Like oftc-hybrid, I intend to link this to OpenSSL. Since nobody > > >> seems to care about that, I'm going to assume that it's OK. > > > > > > People DO care, and it is not OK. Linking with OpenSSL is only allowed > > > if there is an exemption to the license of charybdis that explicitly > > > allows linking to the OpenSSL. See for example this page which gives a > > > nice summary and links to some related debian-legal emails: > > > > > > http://www.gnome.org/~markmc/openssl-and-the-gpl.html > > > > I don't know if it's possible, but you might want to try to link it to > > GNUTLS [1] instead. > > GNUTLS has an OpenSSL portability layer, but it is not complete. It would > require some porting work. > > Btw, the build system in ircd-charybdis considers OpenSSL an optional > dependency. If it's an optional feature, why not just disable it untill a > better solution is found? Because SSL is a requirement for my requirements. I wish to replace inspircd with something that is more suited for my requirements (e.g. something I can use CGI:IRC with, without having ban-evasion issues). We've already found a temporary solution (although I certaintly don't like the side effect that it makes the daemon binary GPLv3), which is to use the portability layer until a native backend for GNUTLS is written (and just simply not have the certificate-based opering feature until it's properly abstracted -- right now it's dependent on libcrypto availability). Obviously a native GNUTLS backend is the best solution, but releasing charybdis 3.0.2 with an openssl.c that can build against gnutls-extra is fine for the immediate future. William
Attachment:
signature.asc
Description: This is a digitally signed message part