yes, the first part is correct, and i like the second part, too! i hope this gets implemented!
also, the first one could be activated repetedly.
also, the others would be installed immediately, and start ticking
Killing the original file would wipe out all of the processes.
yes, the others would be "subprocesses", and killing one would kill all of it's subprocesses.
also, any of them could be killed
however, by "killing", i meant disinfecting
for an example, look at this tree:
(each level represents 1 hour, these are all v0.1)
[brackets represent all processes running]
start install a [a install]
complete install a [a]
a BOMB!(b) [a, b]
a BOMB!(c) b BOMB!(d) [a, b, c, d]
a BOMB!(e) b BOMB!(f) c BOMB!(g) d BOMB!(h) start b disinfect [a, b, c, d, e, f, g, h, b disinfect]
b disinfected, all subprocesses cleared, a BOMB!(i) b BOMB!(neutralized due to disinfect) c BOMB!(j) d BOMB!(neutralized due to disinfect) e BOMB!(k) f BOMB!(neutralized due to disinfect) g BOMB!(l) h BOMB!(neutralized due to disinfect) [a, c, e, g, i, j, k, l]
etc...
make sense?
Perhaps as an additional rub, you could activate it while bouncing THROUGH the server it is installed on to another server, and add a task to the server you are connected to. And the only way to get rid of it is to find the original virus and AV it. If this were to happen, changing IP would kill all the associated tasks on all remote servers.
yes, you could activate it like that, but it would still be able to be removed by disinfecting it, or by disinfecting the processes above it.
yes, an ip change would kill all remote subprocesses, but any remote subprocesses on the changing server would no longer be subprocesses, and could still be activated by the VC.
on that note, if you VC a subprocess, it remains a subprocess, and you also get control of all of its subprocesses
to determine the version of the new process, you would use the formula: version*hours run, and the minimum run time, in hours, by: 1/(version*10), which would create a version 0.1, the minimum. any more time increases the version, and thus the resources of the created subprocesses. however, to prevent abuse, all processes could be disinfected by an AV that could disinfect the first one, or, if their level is lower, by their corresponding malware AV. in other words, a v0.2 created from a v0.1 could be disinfected by a v0.1 AV, but, as another balancer, the AV time should be: v0.1 disinfect time*(level of process to be disinfected+sum of all levels of subprocesses).
also, a v0.1 made from a v0.2 could be disinfected by an AV v0.1.
any other ideas?
one last thing, (i forgot)
P.S. i know this is long.