[Openvas-devel] Start: replacing OpenSSL by GNU/TLS

[Jan-Oliver Wagner]

Hi,

after the infrastructure is back, I'd like to see the coding works
re-start.

The major and most important task, IMHO, is to replace OpenSSL by
GNU/TLS. There is no OpenSSL exception for the server
part. It is therefore illegal to distribute binary packages.

This should be motivation enough to help doing this job ;-)

Please speak up if you offer help (coding, testing, sponsoring
coders, ...). The intitial tasks I see so far are:

- sync openvas-libraries with nessus-libraries
- clean up openvas-libraries (renaming etc)
- replace OpenSSL by OpenVAS (my tests last year
  showed that it will not be sufficient to apply the
  OpenSSL compatibility mode of GNU/TLS for openvas-server;
  probably this holds true for openvas-libraries as well).


One question occured to me:

Does it make sense at all to allow compilation without SSL?
IMHO, SSL should be mandatory, but I'd be happy to stand corrected.

Best

	Jan
 
-- 
Dr. Jan-Oliver Wagner                                   Intevation GmbH
Amtsgericht Osnabrück, HR B 18998             http://www.intevation.de/
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner