[Openvas-discuss] tcp scanner

Jan-Oliver Wagner jan-oliver.wagner at intevation.de
Thu Aug 21 09:52:03 CEST 2008


On Mittwoch, 20. August 2008, Lukas Grunwald wrote:
> >>> thats easy: Pull those C-parts that are not implementable
> >>> in NASL into the
> >>> language/API of  NASL.
> >>>       
> >> Well, we can write a scanner in NASL. It would not be so slow.
> >>     
> >
> > yes, your implementation looks very straight forward :-)
> >
> > openvas_tcp_scanner.c however also collects banners
> > and it tries to give the impression that it is an elegantly
> > performant implementation to cope with firewalls.
> > Not sure how much truth is in this.
> >
> > However, IMHO it is worth establishing a NASL tcp scanner.
> >   
> The problem is, you need very different timings to go with this, and be 
> below triggers of firewalls in some cases, it is not that simple.

thanks for the hint.

That means it does make sense to eventually pull in some
timing tricks into NASL API. Might help for other tests as well.

Personally, I do currently have other priorities, but if any taker
is out there :-)

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



More information about the Openvas-discuss mailing list