Hello Christian, On Mittwoch, 17. September 2008, Christian Eric EDJENGUELE wrote: > so during the week, I've worked on enhancing the openvas plugins development, > I've also seen the way openvas grab software banners, and according to me, > it's > too "hard", and then I've developed a routine to make it more easy, here the > explainations: > > Programming language: python > Modules used: sax, sys, socket, os, re > > Advantages: > 1) software information are stored in xml format, that makes informations > more portable > 2) only one script to parses all banner: http, ssh, telnet, pop3, smtp, etc... > 3) no need to write new script to detect a new software, only add the banner > in the xml file, > I've already done with http.xml, ssh.xml, telnet.xml, pop3.xml, and more ... > 4) Well documented > 5) fast > > Disadvantages: > 1) It's seems openvas does not have a xml parser like sax, but all other > modules exits, and then the code can be easly ported to nasl
Since OpenVAS 2.0, the server is linked to glib. glib offers simple XML parsing which is already used for reading OVAL XML files: http://wald.intevation.org/plugins/scmsvn/viewcvs.php/trunk/openvas-server/openvasd/oval_plugins.c?rev=1434&root=openvas&view=markup I could image to get some xml capabilitis into libnasl. But my mind on this has not settled. Does this influence your conceptual ideas? Best Jan -- Dr. Jan-Oliver Wagner Intevation GmbH, Osnabrück Amtsgericht Osnabrück, HR B 18998 http://www.intevation.de/ Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner _______________________________________________ Openvas-plugins mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-plugins
