ok then,
now let say that you already have 5 configs in the configs_trash
now let say that you already have 5 configs in the configs
you create a new config, it takes id 6 in the configs table
you create the task and associate this new config ...
you delete the task
you delete the config ... it then goes to the configs_trash and get
config id 6 ;-)
so your tasks in the task table still have config id = 6 ;-) (and
hidden = 2)
again new config ... so it take the empty id 6 in configs table
and when you try to modify the configs preference, you can't , because
manage_set_config_preference in manage_sql.c
do a check with :
"SELECT count(*) FROM tasks WHERE config = 6;"
and of course count is 1 (your task is still in the table with the
config = 6)
To my mind the test should be :
"SELECT count(*) FROM tasks WHERE config = 6 and hidden != 2;"
this case you have 0 ;-)
hope you follow me ?
BR
Le 26/09/2012 19:23, Matthew Mundell a écrit :
but at the end i think the question is, when you delete a config,
which
id (not uuid) is put in the config field of the hidden task ?
The task config field should get the ID of the config from
configs_trash.
This looks to work fine here.
--
Greenbone Networks GmbH
Neuer Graben 17, 49074 Osnabrueck, Germany | AG Osnabrueck, HR B
202460
Executive Directors: Lukas Grunwald, Dr. Jan-Oliver Wagner
--
"Le saviez-vous ? la technologie d'ITrust va sécuriser le cloud
français"
| Sébastien AUCOUTURIER | Software Design Engineer Lead
| ITrust | 55 rue l'Occitane BP 67303 31673 LABEGE CEDEX
| Email: [email protected]
| Fixe Sdt. 05.67.34.67.80 | Fax. 09.80.08.37.23
| IT Security Services & SaaS Editor
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
