On Thu, Jul 31, 2003 at 04:00:24PM +0800, zhaohk wrote: > I just installed the Nessus 2.07. ... > #nessus-mkcert <enter> > ... > #nessus-adduser <enter> ... > There is a alert:"Remote host is not using < NSP/1.2 > or is tcpwrapped"
Hmm, I don't recognize that exact error message; are you sure it's accurate? Still, it seems like you have a problem either with tcp_wrappers or, more likely, a mismatch between your client and server regarding SSL/TLS support. Was nessus compiled with support for tcp_wrappers? That is, run "nessusd -d"; does the output say it's present? If so, do your access controls allow for access to the daemon from localhost (eg, "tcpdmatch nessusd localhost")? Alternatively, make sure that the parameter ssl_version agrees between your server configuration (eg, /usr/local/etc/nessusd/nessusd.conf) and your client configuration file (eg, $HOME/.nessusrc). > The second procedure is following: > I enter the four directories in order. > #./configure --enable-unix-socket --enable-tcpwrappers <enter> ... > # nessusd -D > bind() failed : No such file or directory > (make sure /var/run/nessus/nessus.sock does not exist) > > I don't find the file nessus.sock. The daemon is trying to write the socket file in the directory /var/run/nessus when it starts; the error message indicates it can't. Since you say nessus.sock doesn't already exist, then the problem may be simply that the directory doesn't exist. Does it? If it does, is there some reason why the daemon can't create a file there; eg, read-only filesystem, permissions, etc? George -- [EMAIL PROTECTED]
pgp00000.pgp
Description: PGP signature
