> -----Original Message----- > From: Marco Gottini > Sent: Thursday, February 20, 2003 10:54 AM > To: [EMAIL PROTECTED] > Subject: nessus 1.3.4 compling problem - libnasl > [snip] > While doing "make" in libnasl i got an error 'couse > nasl/nasl_crypto.c couldn't fine md2.h. so i made a copy of > /usr/local/include/openssl in /usr/include/openssl (i chose > not to modify nasl/cflags, is it wrong?). > but i still get an error (as well as some usual warnings): > > bash-2.05# make > /bin/sh /tmp/nessus134/libnasl/libtool --silent gcc -pipe -g > -O2 `sh ./cflags` -c nasl_crypto.c [some warnings] [some output] > gcc -pipe -g -O2 `sh ./cflags` -I. > -I/tmp/nessus134/libnasl/include -o nasl -DVERSION=\"1.3.4\" > nasl.c nasl_packet_forgery.o nasl_socket.o nasl_crypto.o > nasl_http.o nasl_host.o nasl_text_utils.o nasl_nessusd_glue.o > nasl_misc_funcs.o capture_packet.o nasl_grammar.tab.o > nasl_tree.o nasl_var.o exec.o nasl_lex_ctxt.o nasl_func.o > nasl_init.o strutils.o regex.o lfind.o nasl_debug.o -lrpcsvc > `/usr/local/bin/nessus-config --libs` > nasl_crypto.o: In function `nasl_md2': > /tmp/nessus134/libnasl/nasl/nasl_crypto.c:75: undefined > reference to `MD2' > nasl_crypto.o: In function `nasl_hmac_md2': > /tmp/nessus134/libnasl/nasl/nasl_crypto.c:219: undefined > reference to `EVP_md2' > collect2: ld returned 1 exit status > make: *** [nasl] Error 1
with the help of a friend i found an "escamotage" to solve the problem. it's not the best way, but i works. the main error was gerated by openSSL: for some reasons it didn't create libcrypto.so and related dynamic libraries (but while compiling NO error was given). I noticed that the new OpenSSL version uses different paths comparing to older versions. so i modified nessus-config to link to the static library in the right path. finally nessusd daemon starts without any problem. BUT after calling nessus-update-plugins nessus gives an error/warning: 2 plugins (unknown_services and trojan_horses) have too many dependecies (282). nessus seems to work fine, but i'm a bit worried by this new problem. Any suggestion? many thanx, Marco
