Re: Need more vuln information on Nessus PluginID 15640

One more question, we're trying to reproduce this finding with :
Via the normal nessus command we do get the finding, but running the 
individual .nasl script we don't

nasl -t 10.0.0.1 http_url_format_string.nasl

But the finding was on port 443, and the above doese not pick up on that.
If we change the port 80 to port 443 inside the script does not help 
either, no response.
So I'm assuming that there is some ssl functions missing.
Is there a way to get the above command to run properly, including any 
ssl functions required and on port 443 ?

Or can you explain how the mechanism works, testing http nasls on ssl ports

Thanks Oskar


George A. Theall wrote:

> On Tue, Dec 12, 2006 at 02:03:20PM +0100, oskar wrote:
>
> > One more question, where do set the debug level to 1 ?
> >
> > Checked nessusd.conf, manual page of nessusd and manual page of 
> > nessus, but none have a reference to setting of the debuglevel.
>
>
> It's a global preference setting. So if you're using NessusClient, 
> look  on the "Options" tab, under "Prefs." / "Global variable settings".
>
> George

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus