I just commited 3com_hub replacement to trunk. That means most old vulnerability checks implemented in C are now implemented in NASL. As they are old I was limited in testing them, so if you can test it more, it would be appreciated. (I have found single 3com switch, could find any other 3com model, and I don't have SGI box to test SGI objectserver vuln...)
That means we still have following generic plugins to replace: * portscanners (tcp/syn) - should be replaced by nmap? * ssl_ciphers - SSL implementation missing, basic SSLv2 implementation in ssl_funcs.inc, but for this we need SSLv2 and SSLv3 implementation. Should we implement SSL in NASL or use openssl/gnutls and export useful f() to NASL? * find_service - part of CR#40, http://www.openvas.org/openvas-cr-40.html Also here's something that was discovered during C plugins replacement development: - openvas NASL is missing layer 2 functions (in order to implement 3com_hub fully in NASL, it is required to have layer 2 functions) - openvas NASL is missing network info functions (what mac addres, what subnet, what interface packet will go through, ...). It could be done using pread and parsing output from ifconfig/route/, but it seems clumsy and not portable. Kost _______________________________________________ Openvas-devel mailing list Openvas-devel@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
