Ideally, what I would like to do is: a)Use existing code from Nessconnect to use NTP b)Adapt Nessconnect code to provide another implementation which uses OTP c)Write a third implementation for OMP
Using the spring framework, I could do this in such a way that it is easy to switch from either implementation. This is quite a wee bit of work probably but the end result would be that I could write additional code that does analysis of the data and interfaces with the likes of Metasploit through plugins I could write in Ruby for that. Ultimately, I'd like my own Pen testing framework that can remember scans, match scan results to exploits, and remember which exploits were successful so that its simply a case of point and click when repeating. If anyone has any ideas on this or wants to talk about it further I would be very pleased to hear what anyone has to say! Derek. -------------------------------------------------- From: "Thomas Reinke" <[email protected]> Sent: Monday, October 18, 2010 11:18 PM To: <[email protected]> Subject: Re: [Openvas-discuss] Openvas-client as a nessus client > Thomas *smacks* self and reminds self to read the _entire_ thread before > replying! > >> But if I was writing or adapting an NTP based java client surely I could >> code it in such a way that it could switch between NTP and OTP... > would this >> be enough for the client to work with Nessus and OpenVAS??? >> >> Derek. > > The changes to the protocol are minor. If you are familiar with one > protocol, the changes to implement the other is trivial. (Hint - we > have a stripped down custom client, for both OTP/NTP, and the code > changes between the two different clients amount to 5 lines of code.) > > The responses between the two will probably start to diverge more > and more over time, so you may want to put some thought into what > you will do as the OTP protocol changes and migrates further away > from NTP. > > Thomas > > Thomas Reinke wrote: >> The protocols are not compatible with each other, so no, you cannot >> use openvas-client on nessusd or nessus client against openvassd. >> >> Thomas >> >> >> Stefano Gargiulo wrote: >>> Hi, in debian packages openvas-client replaced nessus client. >>> >>> Now i'm asking, can i use openvas-client as a nessus client (against a >>> nessus 4 server?) >>> >>> How to specify the protocolo version to nessus and not openvas? i can't >>> find this in the man. >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Openvas-discuss mailing list >>> [email protected] >>> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >> >> _______________________________________________ >> Openvas-discuss mailing list >> [email protected] >> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >> > > _______________________________________________ > Openvas-discuss mailing list > [email protected] > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > _______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
