Nothin'

[whef]

Just close, please. I ****** up with the "so called exploit", what then wasnt. 

[ãłþħά-∆9]

Bretty weird indeed. 

I'm not surprised bugs like that still exist, noone uses the tasklist really anyway, I think it needs a nice update.

Such as: You can set protections to the task list, simply click run on the task and it'll run them... So i can put firewall, password, IP cloaker and unhider on a task, then simply click run to run them all at once....

Good if you're super lazy, thats about it 


Also exploit wise... You can start to delete a file, then run it then delete it and it'll still be running, I do it to my log deleter to stop it being stolen, disadvantage is once the process is closed, you need to get the program again, easy if you have gold FTP

[whef]

But hard to get if you dont. 

[Brok Ironfist]

This has been known for a while and hasn't been a problem.

I basically see it as this:  The file has been loaded into memory and the file on the drive no longer matters.  As long as the process isn't canceled you are all set.  But if it is canceled then you have to reload it, and if it's been hidden, encrypted or even deleted then you are out of luck.


This is actually how many files work in real life on computers.  You could load a word document into memory and delete the actual file.  As long as the process hasn't been canceled then you are all set.

[bontrose]

yes but there is a safety mechanism that stops you from deleting while open in word

[ãłþħά-∆9]

The trick is to delete it then run it, rather than the opposite, wouldn't work in real computers because deletes are instantaneous

[Exousia]

Locked as per OP request.