logsys, on 19 May 2014 - 04:41 PM, said:
apemanzilla, on 19 May 2014 - 04:30 PM, said:
logsys, on 19 May 2014 - 04:18 PM, said:
Thats also true, but let's not consider a disk as a method to engage the "anti-virus" cause there is no possible way of tricking the anti-virus, unless you know what anti-virus you are dealing with and then possibly mutate you code so it doesn't detect it.. also, if it had an AI, it could manage to not being deleted
1. You mean virus.
2. If you boot it from a disk with a blank startup, the virus can't do crap unless you run it manually.
3. It can't touch your code unless you start it manually, see above.
4. Why would there be an AI again?
1. True
2. Also true, but again, that overrides the main startup, where in a normal computer(irl) it doesn't.
3. "mutate your code so it doesn't detect it"
4. The AI would mutate the code so, if ran a anti-virus(instead of a blank startup) it would survive the "murder" attempt
2. This is computercraft, and a disk with a startup file
ALWAYS takes priority over the built in startup. So, make a new disk with a blank computer, attach it, and boot the computer and you've got normal shell with unrestricted access again.
3. Hiding files from the code involves overriding the fs and io APIs, which is not reboot-safe so it requires code to be re-run very time it boots. If you boot from an uninflected disk, you don't have that problem.
4. That wouldn't be an AI. An AI learns as it is exposed to new things generally. This is simply an automated task that runs whenever a disk is connected.
Additionally, running "rm *" in the shell should accomplish the same task as this.
Edited by apemanzilla, 19 May 2014 - 07:23 PM.