Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Nessus-Users
[Top] [All Lists]

Re: nessus-mkcert and client

Subject: Re: nessus-mkcert and client
Date: Mon, 10 Apr 2006 09:47:17 -0400
On Mon, Apr 10, 2006 at 12:07:35AM +0000, mudyo26 CryptoMail User  wrote:

If nessus server and client are on the same host , do we need to run nessus-mkcert ? and nessus-mkcert-client ?( Nessus version 3.0.2)

Use nessus-mkcert if you want to encrypt communications between the client and server using SSL / TLS1. This is how Nessus expects to operate by default. If you're not concerned about this (eg, because your client and server are on the same machine), you could set "ssl_version = NONE" in nessusd.conf as well as in your client config(s) to have traffic unencrypted. This setting affects the server in general, so if you anticipate needing to use a remote client, this would not be a good idea.


nessus-mkcert-client is needed only if you want to authenticate Nessus users with a certificate rather than a password.

In case nessus-mkcert-client has to be run , to which directory are the output 
files copied?
What are the steps to do that.

The client key / cert, key_${user}.pem and cert_${user}.pem respectively, are left in a scratch directory, which will be reported when you run nessus-mkcert-client. They will need to be copied manually somewhere that the client can access. Personally, I use ~${user}/.nessus, but anywhere will work.


George
--
theall@tenablesecurity.com
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

<Prev in Thread] Current Thread [Next in Thread>