Hi everyone, we experienced exactly the same problem here. It happens in OpenVAS 8 (Debian8, Debian 9) as well as in OpenVAS 9 (Kali rolling release).
I did report that to this mailing list, but didn't get any response. Best regards Christian Ebert Chief Security Analyst, CISM, T.I.S.P. Head of Penetration Testing QSC AG Mathias-Brüggen-Straße 55 50829 Köln T +49 221 669-8950 F +49 221 669-85950 M +49 163 6698950 [email protected] http://www.qsc.de Besuchen Sie unsere Blogs: Corporate Blog unter http://blog.qsc.de Themen-Blog zur Digitalisierung unter http://digitales-wirtschaftswunder.de Bitte finden Sie hier die handelsrechtlichen Pflichtangaben: http://www.qsc.de/pflichtangaben Am 09.06.2017 um 08:46 schrieb r.m6 <[email protected]>: Dear openVAS Community, we are using an openVAS 8 installation (ubuntu 16.04 server) with multiple scan interfaces (eth0, gre1, gre2) for vulnerability scanning. Some tasks are configured for "Network Source Interface" (in the Web UI "Edit Task" dialog) eth0, some others for gre.... We have observed that if the field "Network Source Interface" is (by accident) left blank when creating a new or editing an existing task, openVAS resets ALL other existing tasks for all OTHER openVAS user accounts on this openVAS instance to blank. This results in scanning from eth0 (the default) for ALL existing tasks - which is extremely annoying for scheduled tasks because the results are messed up, alerts are sent (because of the changed scan score) and each user has to repair each single task. Did anyone else observe this behavior or - preferred :) - has a solution for this problem? Many thanks in advance! _______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
