Leave off the //client and //nessus - those are just comments telling you the so.4 is for the client and the so.6 is for the server.
Printable View
My bad for not being clear, as DaKahuna posted, the "//client" and "//server" tags were just for clarification as to what links are for what. As far as your ldconfig output, I got the same thing when I ran ldconfig after installing nessus, I think you can safely ignore it...
E
Thanks guys. Ill test drive it in the morning.
So I finally got it going but now there is no place to put in your credentials in the new GUI. Maybe Im just tired but some one please help me out
EDIT: never mind I found it .I'm a dumb ass and I should be publicly ridiculed and stoned in the town square
When I start Nessusclient and try to connect to localhost, it cannot find nessus server.
I think there's something wrong with my config... i cannot find the "old-style" "nessusd".
Can someone help me?
EDIT:
Forget...didn't exported the PATH var :P
It still works as nessusd for me. The only thing I did different in the tutorial was installed the nessus libraries and I had to create some extra links for nessus fetch and the plugin updater. Other than that it works.
I did everything according to this tutorial. I updated all the files accoardingly. When I try to run it I keep gettiung this error:
bt sbin # export PATH=$PATH:/opt/nessus/sbin:/opt/nessus/bin:
bt sbin # nessus-mkcert
./nessus-mkcert: line 92: 18182 Floating point exception$sbindir/nessusd -g
Executing nessusd failed. Make sure your library loader is configured properly
and that nessusd is in your $PATH
I would appreciate any help.
Did you run ldconfig when you were done? What version of openssl are you using?
Code:# openssl
openssl> version