[Openvas-devel] Start: replacing OpenSSL by GNU/TLS
Norm.Donovan at Sentrik.com
Mon Mar 26 16:58:14 CEST 2007
Is GNU/TLS GPLv2 or "GPL and any future version" and thus would become GPLv3. I thought Nessus is GPLv2. Would mixing v2 and v3 create issues?
From: openvas-devel-bounces at wald.intevation.org [mailto:openvas-devel-bounces at wald.intevation.org] On Behalf Of Tim Brown
Sent: Monday, March 26, 2007 7:49 AM
To: openvas-devel at wald.intevation.org
Subject: Re: [Openvas-devel] Start: replacing OpenSSL by GNU/TLS
On Monday 26 March 2007 15:26, Daniel Cabezas wrote:
> Don´t want to talk much about an issue which I don´t know well, but why
> aren´t other alternatives studied? I mean, like matrixssl. That stub of
> wrapper functions could make any underlying ssl engine work, and the binary
> deployment responsible would be able to choose which library to link
> openvas against.
This is a fair point, although the counter would be, that we don't want to end
up support 1001 different SSL implementations and openssl and gnu/tls are the
most well known and widely deployed so far.
I vote we do a stub with support for OpenSSL and GNU/TLS and let folk who want
to use something else (Win32 SSLs etc worry about that for themselves). Note
I also think the stub should map to GNU/TLS and that we figure out the APIs
required for OpenSSL to be made to behave in the same manner.
MatrixSSL looks interesting, but may cause issues for any commercial users of
the future OpenVAS:
"Basically, the dual license means that you can use the library for free as
long as you make public all code that links with it or otherwise uses the
library. In addition, any changes made to the library must also be made
public. If the application source code using MatrixSSL is to remain
proprietary, a commercial license can be purchased from PeerSec Networks, the
authors of MatrixSSL.".
<mailto:timb at nth-dimension.org.uk>
Openvas-devel mailing list
Openvas-devel at wald.intevation.org
More information about the Openvas-devel