I have received a few private replies expressing curiousity about this
same thing. Thus, I figured I'd summarize to the list.
Thanks to a couple of other replies, I've got it working. I do *not* have
it working with encryption between the client and server. This could
probably be done with stunnel, but I didn't fool with it. I'm working on a
private network and just doing some testing, so for now, client/server
encryption wasn't a big issue. Here's how I did it:
* Set the variable force_pubkey_auth to "no" in nessusd.conf on the
server.
* Add a user on the server (nessus-adduser) with the auth type of
plaintext.
* On the client, do: telnet NESSUS_SERVER 3001
* _Immediately_ upon connect, send: < NTP/1.2 >
* As it should, the server will respond with the NTP version.
* The server will then prompt for a user/password, and upon auth
(plaintext) it will dump its plugin set and config.
Seems to work great! Thanks! :)
~Jay
On Wed, 6 Feb 2002, Jay wrote:
>
> Part of the "nessus-core" docs (1.0.10) is a great NTP whitepaper. This
> shows the NTP commands between client/server and an example typical
> client/server session (section 4 at the end).
>
> This leads me to believe that I should be able to telnet to the nessus
> server on port 1241 and enter commands - basically acting like a manual
> client. However, when I telnet to either 1241 or 3001 on a 1.0.10 server,
> it connects then disconnects a few seconds later without any output from
> the server.
>
> Has anyone else tried this (acting like a client - manually entering
> commands)? Is there a trick I'm missing?
>
>
--
~Jay
