On Thursday 26 November 2009 01:22:24 Tim Brown wrote: > Stephan, regarding the overflows, I saw only two reported.. one where > sizeof was being called on the wrong structure and one where pointer > arithmetic might be suspect within a loop. I believe the former has been > fixed already in trunk, did I miss another one?
Sorry Tim, I screwed it up (Felix' new upload for -libaries fixed some). The only issue our code checks currently find is in openvas-scanner: I: Statement is overflowing a buffer E: openvas-scanner bufferoverflow openvas_tcp_scanner.c:518 I triggered new builds for -libraries and -client, please see https://build.opensuse.org/project/monitor?project=security%3Aopenvas%3AUNSTABLE for the details. Regards, Stephan _______________________________________________ Openvas-devel mailing list Openvas-devel@wald.intevation.org http://lists.wald.intevation.org/mailman/listinfo/openvas-devel
