On Fri, 2004-04-30 at 16:07, George Theall wrote:
> The trace suggests you're calling the plugin by invoking nasl at the
> commandline. If so, realize that this method doesn't give plugins
> access to KBs, which plugins such as this require.
right - I've re-run the scan using the client and get the same output..
not vulnerable && it should be reported as vuln.
here's the content of the kb:
1083593490 3 Launched/10180=1
1083593490 1 SentData/10180/INFO/1=The remote host is up
1083593490 1 Success/10180=1
1083593491 3 Launched/10330=1
1083593491 1 SSL/password=
1083593491 3 Launched/12204=1
1083593491 3 Launched/11011=1
1083593491 1 Known/tcp/139=smb
1083593491 1 Services/smb=139
1083593491 1 SentData/11011/INFO/1=An SMB server is running on this port
1083593491 1 Success/11011=1
1083593491 1 SMB/transport=139
1083593491 3 Launched/12209=1
This is Nessus 2.0.10 for Linux 2.4.20-28.9
compiled with gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
Current setup :
Experimental session-saving : enabled
Experimental KB saving : enabled
Thread manager : fork
nasl : 2.0.10
libnessus : 2.0.10
SSL support : enabled
SSL is used for client / server communication
Running as euid : 0
thanks,
tan
_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus
