apparent flaw in nessus-mkcert-client

[Don Whiteside]

Or perhaps this is on purpose.

when using mkcert-client and using the option to register the newly generated cert in the users database, the script doesn't ask for rules (no big deal) but also doesn't create an empty rules file to go with the dname entry.

Subsequent attempts to connect yield an ambiguous (at least from nessusWX) error 'invalid username or password supplied' when in fact the problem is nessusd can't find the rules file.

nessusd will also complain to the console about the lack of a plugins directory for that user but it will let them log in.

-
[EMAIL PROTECTED]: general discussions about Nessus.
* To unsubscribe, send a mail to [EMAIL PROTECTED] with
"unsubscribe nessus" in the body.