it's not a bug, it's normal feature and normal functionality. Eero
2017-07-28 14:56 GMT+03:00 Rémi Liquete <[email protected]>: > Hi Christian, > > This is exactly what I have tested yesterday, and after a day of work > where everything was working fine, I've putted this in production. > And in production, the task starts. > > The problem is, when the task has been started (and is no longer in status > "New") we can't modify the target of the task. I'm in OpenVAS 9, and I > don't know if this has been changed from OpenVAS 8 to OpenVAS 9. > The OMP command exit with error code like : target is immutable as long as > the status is not "New". > > Regards, > Rémi. > > 2017-07-28 13:08 GMT+02:00 Ebert, Christian <[email protected]>: > >> Hi everyone, >> >> >> >> we had a similar problem: >> >> >> >> We had to modify the port list of **many** targets without loosing the >> results oft he previous scans. >> >> >> >> Our solution works as follows (OpenVAS 8): >> >> >> >> - Make sure, all task are created as „alterable“ >> >> - Create a dummy target >> >> - Modify the task and give it the dummy target >> >> - Mofify the orgininal task (portlist or …) >> >> - Modify the task again and give it the modified target >> >> >> >> Maybe this can help. >> >> >> >> 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 <+49%20221%206698950> >> >> F +49 221 669-85950 <+49%20221%2066985950> >> >> M +49 163 6698950 <+49%20163%206698950> >> >> [email protected] >> >> http://www.qsc.de >> >> >> >> Besuchen Sie unsere Blogs: >> Corporate Blog unter *http://blog.qsc.de <http://blog.qsc.de/>* >> Themen-Blog zur Digitalisierung unter *http://digitales-wirtschaftswunder.de >> <http://digitales-wirtschaftswunder.de/>* >> >> >> >> Bitte finden Sie hier die handelsrechtlichen Pflichtangaben: >> >> http://www.qsc.de/pflichtangaben >> >> >> >> *Von:* Openvas-discuss [mailto:openvas-discuss-bounce >> [email protected]] *Im Auftrag von *Rémi Liquete >> *Gesendet:* Donnerstag, 27. Juli 2017 20:13 >> *An:* Eero Volotinen <[email protected]> >> *Cc:* [email protected] >> *Betreff:* Re: [Openvas-discuss] Keep report after deleting task >> >> >> >> Ok, I will. >> >> >> >> Thanks for you time and your help :) >> >> >> >> Regards, >> >> Rémi >> >> >> >> Le 27 juil. 2017 8:00 PM, "Eero Volotinen" <[email protected]> a >> écrit : >> >> that might require major modifications to sourcecode. >> >> >> >> ask commercial consulting from greebone? >> >> >> >> Eero >> >> >> >> 27.7.2017 5.42 ip. "Rémi Liquete" <[email protected]> kirjoitti: >> >> Hi, >> >> >> >> I'm getting crazy right now :(. >> >> >> >> I made a task alterable so I could change the target. >> >> >> >> However, when the task is no longer "new", I cannot change the target of >> the task anymore. >> >> >> >> I tried to see what's possible to do in source code but this is a bit >> crazy to get in right now. >> >> >> >> So, is really no solution for my need? >> >> To remember, here is what I need in other words : >> >> Before each scan, I have to change my port lists and my targets. For >> doing it, I have to delete the task linked. >> >> The problem is when I delete the tasks, I lost reports associated in >> greenbone web interface. >> >> This is a real problem as I have to keep these reports in greenbone web >> interface. >> >> >> >> Regards, >> >> Rémi >> >> >> >> Le 26 juil. 2017 5:01 PM, "Rémi Liquete" <[email protected]> a écrit : >> >> I'm creating new tasks on each run because I can't modify port list and >> target while the task they are linked to is not deleted. >> >> This is why I have to create tasks on each run, and doing it, delete also >> my reports. >> >> So I think I have to check the source code :(. >> >> >> >> Regards, >> >> Rémi >> >> >> >> 2017-07-26 16:58 GMT+02:00 Eero Volotinen <[email protected]>: >> >> that might not be possible without modifications to source code? >> >> >> >> how about creating new task on each run? >> >> >> >> Eero >> >> >> >> 2017-07-26 17:56 GMT+03:00 Rémi Liquete <[email protected]>: >> >> I'm already creating task with scripts. >> >> The goal is to keep reports in Greenbone (and not in disk) when I delete >> the task. >> >> Regards, >> >> Rémi. >> >> >> >> >> >> 2017-07-26 16:44 GMT+02:00 Eero Volotinen <[email protected]>: >> >> How about creating tasks with scripts and deleting old results after >> saving reports to disk? >> >> >> >> or creating new task on each scan. >> >> >> >> Eero >> >> >> >> 2017-07-26 13:02 GMT+03:00 Rémi Liquete <[email protected]>: >> >> Hi, >> >> I'm creating a script based on PfSense Backup to create ports lists, >> tagets and tasks because these parameters are changing every day. >> >> As it's impossible to modify ports lists and targets while they are in >> use, I have to delete what I've created each time the task is complete. >> >> However I would like to keep reports generated by the tasks when I delete >> those tasks. >> >> I'm able to get the reports in the server, but I would like to keep these >> in Greenbone interface, as long as other IT have to access to it (with >> proper permissions). >> >> So the question is : >> >> It is possible to keep reports when deleting tasks ? >> >> Or is any way to modify ports lists and targets while in use so I have >> not to delete tasks. >> >> >> >> Regards, >> >> Rémi >> >> >> >> _______________________________________________ >> Openvas-discuss mailing list >> [email protected] >> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/o >> penvas-discuss >> >> >> >> >> >> >> >> >> >> >
_______________________________________________ Openvas-discuss mailing list [email protected] https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
