On 07/12/12 22:13, Francesco Poli (wintermute) wrote: > The possible solutions I can think of are: > > A) ntop is modified so that it can link with GNUTLS, instead > of OpenSSL > > B) an OpenSSL linking exception is granted to all the relevant > files by the respective copyright holders and also to > the FSF's GNU DBM library by its copyright holders (I don't > know how much this is likely to happen, though...)
Hello, a 3rd solution is to recompile without ssl support. The functions in ssl_utils.c are only called inside webInterface.c and httpd.c. So I suppose that disabling ssl will only disable the https support for the web interface of ntop. This is easily done, adding a single line in debian/rules. See patch in attachment. After applying the patch, I was able to recreate a deb package and install it. An ldd against /usr/bin/ntop does not reference libssl anymore. As expected the option to specify the https port is not available anymore on the ntop configuration page. Cheers. -- Giovanni Rapagnani
--- debian/rules-old 2012-11-30 09:37:15.000000000 +0100 +++ debian/rules 2013-02-09 17:15:23.982176250 +0100 @@ -11,6 +11,7 @@ ./autogen.sh \ --prefix=/usr --bindir=/usr/sbin --libdir=/usr/lib/ntop \ --sysconfdir=/usr/share --localstatedir=/var/lib \ + --without-ssl \ $(shell dpkg-buildflags --export=configure)
