Re: NTP/1.2 Dependencies Format

Hi Janos,

Thanks for reporting this to us -- this indeed is a Nessus 3 for  
Windows problem (the output on Unix is the same as in 2.x). We'll get  
that fixed in a new build.

Nevertheless, you do not want to expose the plugins dependencies to  
the end-user. The dependency tree is fairly complex and the option  
'auto_enable_dependencies' should be in charge in enabling the  
relevant plugins.


                                    -- Renaud



On Jan 31, 2008, at 4:52 PM, Janos Szatmary wrote:

> Did NTP/1.2 change between version 2 and 3 of Nessus?
>
> I noticed that under version 2 the dependencies were reported as the  
> name of the plugin, while under version 3 they are reported as the  
> name of the script. Since the name of the script is not included in  
> the plugin information, this seems somewhat useless. Is there a way  
> to get the name of the script for a plugin via some NTP option? I  
> don’t see any new protocol options that would include this as part  
> of the plugin data…
>
> See below:
>
> Nessus 2.x: LinkSys EtherFast Router Denial of Service Attack <|>  
> Services <|>
> Nessus 3.x: LinkSys EtherFast Router Denial of Service Attack <|>  
> find_service.nes <|>
>
> Thanks,
>
> John
>
> _______________________________________________
> Nessus mailing list
> Nessus@list.nessus.org
> http://mail.nessus.org/mailman/listinfo/nessus

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