On Wed, 13 Feb 2002, Cristobal Soto wrote: > Alternatively I tried to telnet the nessusd server myself and sent "< > NTP/1.2 >" but the connection closed inmediately.
Here is the problem. One of the shortcomings of the Python script (as it stands today) is that it has to connect to the nessusd server clear text. Doing a manual telnet to the nessusd server and entering "< NTP/1.2 >" (without the quotes) is a good test to make sure that works. The server should then prompt you for a username/password. If that doesn't work, then check out your /usr/local/etc/nessus/nessusd.conf file on the server. There should be an option called "force_pubkey_auth = yes" -- just comment out (#) that line and reload nessusd. You should then be able to make the telnet connection. As a general reminder/note - everything sent with telnet is clear text. Hopefully in the future my Python script will support certs and keys for auth - but for now, it doesn't. Hope that helps! :) ~Jay > > Finally i tried > nessus -pq localhost 1241 <validuser> <validpasswd> > > and it says "nessus: invalid option -- p" > > should i try the CVS version? Im running nessus 1.1.12 > > Thanks > Cristobal > > Renaud Deraison wrote: > > > > On Tue, Feb 12, 2002 at 02:09:47PM -0500, Dmitriy Kropivnitskiy wrote: > > > For my uses of nessus, making a separate interactive > > > CLI interface would not help things, since it will not > > > generate nessusrc automagically. My suggestion ( not sure > > > if it is easily implementable ) would be to make a separate > > > program/script that would pull current .nessusrc in, pull current > > > plugin list, find differences and insert new plugins according to > > > some kind of a rule set. > > > > You can retrieve the list of plugins from the remote nessusd server > > by doing > > nessus -pq nessusd_host 1241 login password > > > > That's a start - feel free to write the rest ;) > > > > -- Renaud > > -- ~Jay
