On Fri, Mar 28, 2003 at 03:53:51AM -0800, JC wrote:

> I didn't want an opinion I although I would have taken one, but what I
> was looking for was 'specify the pass phrase at the command line with
> the -k option or specify private_key_passphrase =
> "somevery_very-very-very-very-very-very Secure passphrase" in your
> .nessusrc ' even the classic "Duly Noted" would have been sufficient.

I'm sorry my reply wasn't what you were looking for, but other than
provide a description of your environment, your message essentially
asked only "can someone help me understand why private key encryption is
not being used?"

Now, if I understand your problem correctly, you'd like to figure out
how to use nessus with an encrypted private key.  If so, it's trivial -
just specify the pass phrase on the commandline between the user and
target arguments.  While the documentation says this is to be the
"password", the client actually regards it as the pass phrase when using
an encrypted private key. 

> If you just build Nessus from scratch, you run the nessus-mkcert, now
> you run the nessus-mkcert-client. Everything works and you go to the
> /tmp folder with the files and crypt your key with the command above.
> Then you specify your key_file and cert_file in your .nessusrc and try
> to connect to the server you'll get something like this
>  
> [$PREFIX]/nessus/users/[username]/auth/password: No such file or
> directory

Assuming you tried specifying the pass phrase, did you also get a
message saying something like:

   Given DN=[blah]/[EMAIL PROTECTED]
   Known DN=[blah]/[EMAIL PROTECTED]

before the error about auth/password? If so, you need to modify the file
auth/dname to use the DN in the format passed in by the client. 

Finally, if you haven't done so already, you must run nessus-adduser to
create the necessary files for the user and notify the daemon of the
change.  This should be run before nessus-mkcert-client, so if you
didn't, you will need to re-edit auth/dname and ensure it specifies the
correct DN. 

George
-- 
[EMAIL PROTECTED]

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to