162 posts
453 posts
Holland
162 posts
779 posts
Kerbin
463 posts
Germany
well that rednet stuff is deleted anyway then.break will change ID's, for some rednet stuff you might not want that
779 posts
Kerbin
In 10 seconds?well that rednet stuff is deleted anyway then.break will change ID's, for some rednet stuff you might not want that
I never needed this, no one ever needed this, this shouldn't be even called a program. You think people are gonna search your forum thread to download some code snippet to erase all their data? No. No one will. Your program can be replicated in 10 seconds.
162 posts
I built this program for newbies who don't know this, you already were one of them, weren't you?In 10 seconds?well that rednet stuff is deleted anyway then.break will change ID's, for some rednet stuff you might not want that
I never needed this, no one ever needed this, this shouldn't be even called a program. You think people are gonna search your forum thread to download some code snippet to erase all their data? No. No one will. Your program can be replicated in 10 seconds.
Download is 2 seconds :-)
But you're right, this program is useless.
1610 posts
Format Utility
A really simple utility! Just run and it deletes everything!(Except Read-Only files)
Good for OS uninstall and hidden files erasing(including virus)
Download: pastebin run ze5FEEU7
162 posts
Format Utility
A really simple utility! Just run and it deletes everything!(Except Read-Only files)
Good for OS uninstall and hidden files erasing(including virus)
Download: pastebin run ze5FEEU7
A well coded virus could easily hide itself and prevent deletion of itself.
1610 posts
Not true. A smart user could easily remove said virus with a disk.Format Utility
A really simple utility! Just run and it deletes everything!(Except Read-Only files)
Good for OS uninstall and hidden files erasing(including virus)
Download: pastebin run ze5FEEU7
A well coded virus could easily hide itself and prevent deletion of itself.
Those virus would not be able to be removed in anyway, but deleting on the world folder or just breaking the computer, although that will change the ID as mentioned before
162 posts
Not true. A smart user could easily remove said virus with a disk.Format Utility
A really simple utility! Just run and it deletes everything!(Except Read-Only files)
Good for OS uninstall and hidden files erasing(including virus)
Download: pastebin run ze5FEEU7
A well coded virus could easily hide itself and prevent deletion of itself.
Those virus would not be able to be removed in anyway, but deleting on the world folder or just breaking the computer, although that will change the ID as mentioned before
1610 posts
1. You mean virus.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
162 posts
1. True1. You mean virus.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
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?
1610 posts
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.1. True1. You mean virus.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
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?
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
162 posts
3. If you programmed you virus to appear to be a program that wouldn't be suspicious, if a anti-virus was ran it would not detect, because the anti-virus ill check if the code matches, changing a bit will confuse the anti-virus.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.1. True1. You mean virus.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
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?
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
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.
1281 posts
This would still require you to override the fs API, meaning you'd be better off just preventing acess to it through fs at all.3. If you programmed you virus to appear to be a program that wouldn't be suspicious, if a anti-virus was ran it would not detect, because the anti-virus ill check if the code matches, changing a bit will confuse the anti-virus.
1610 posts
…and to override the fs API you would need to have code run before the user starts messing with it, which means a disk with a blank startup still comes out on top.This would still require you to override the fs API, meaning you'd be better off just preventing acess to it through fs at all.3. If you programmed you virus to appear to be a program that wouldn't be suspicious, if a anti-virus was ran it would not detect, because the anti-virus ill check if the code matches, changing a bit will confuse the anti-virus.
779 posts
Kerbin
7508 posts
Australia
Disk drive on top with a black startup disk. bypassed.Just unload fs API:
os.unloadAPI("fs")
And unload os API:
os.unloadAPI("os") (XD)
And done… You can't reboot the computer, the edit don't works, you can't do anything to delete it…
1610 posts
1610 posts
Not what I meant, I meant I couldn't remember if it unloaded the APIs globally or for the current environment only.For me os.unloadAPI worked.
779 posts
Kerbin
162 posts
The virus I found has to do with that, but it can't be bypassed after correctly triggered(log out and log in or chunk unloading should work to bypass). It also can prevent other computers from turning on even. So I guess, now that I am thinking, the virus I found will, probably, not be getting fix, just the vm crash, which disabled the bypassGlobally, naturally :-)
os.loadAPI loads the API globally
os.unloadAPI unloads the API globally
1610 posts
Are you sure? By globally I mean across all function environments. Because, arguably, as long as any one environment has access to the unloaded functions and the current one has access to getfenv, setfenv, and pcall, you can always get access to the APIs again.Globally, naturally :-)
os.loadAPI loads the API globally
os.unloadAPI unloads the API globally
779 posts
Kerbin
1610 posts
You're not understanding it. If you unload it for only that ENVIRONMENT, the coroutine or function cannot access it but others can. If you unload it GLOBALLY, NOTHING can access it.If you unload an API that computer can't use that API to next API loading.
I don't know what is getfenv or setfenv, but as I know pcall() is a Lua function, and as I know you can't unload Lua's functions.
1610 posts
Absolutely not. On environment is one set of functions for a thread or function to use.One ENVIRONMENT is one terminal?
779 posts
Kerbin
1610 posts
No, and even if it did it would still have nothing to do with a CC terminal.Sorry, I thought Environment = Integrated Development Environment
779 posts
Kerbin
7508 posts
Australia
doesn't matter. run this code-snip unload in env statements-
print(getfenv(0)['fs']) --# bios.lua env
print(getfenv(1)['fs']) --# shell env
print(getfenv(2)['fs']) --# program env
getfenv(2)['fs'] = nil
print(getfenv(0)['fs'])
print(getfenv(1)['fs'])
print(getfenv(2)['fs'])
1610 posts
I'd also want to point out that this should only happen because tables are passed via pointer. If you take a hard copy of the table, it should be safe from environment hacks like the above.doesn't matter. run this code-snip unload in env statements-doesn't matter what env you nil it, whether its the bios env or the program env, its gone. why do you think that when newbies override a function like read the shell and/or bios gets effected?print(getfenv(0)['fs']) --# bios.lua env print(getfenv(1)['fs']) --# shell env print(getfenv(2)['fs']) --# program env getfenv(2)['fs'] = nil print(getfenv(0)['fs']) print(getfenv(1)['fs']) print(getfenv(2)['fs'])
463 posts
Germany
Thats true, tables are passed byref, and it's good that they're passed like that. Any type of synced thing would require global environments otherwise, which CC doesn't like it seems. (Global table is "read-only" (rawset!), has a protected metatable, every program modifies it's own environment instead of _G, and the environment has _G as an index)I'd also want to point out that this should only happen because tables are passed via pointer. If you take a hard copy of the table, it should be safe from environment hacks like the above.
1610 posts
And the functionality of this program can be recreated with five key presses in CraftOS anyways.Thats true, tables are passed byref, and it's good that they're passed like that. Any type of synced thing would require global environments otherwise, which CC doesn't like it seems. (Global table is "read-only" (rawset!), has a protected metatable, every program modifies it's own environment instead of _G, and the environment has _G as an index)I'd also want to point out that this should only happen because tables are passed via pointer. If you take a hard copy of the table, it should be safe from environment hacks like the above.
As the "developer" said this program is for cc noobs: People are using CC because they want to program. Not because they want stuff to delete their virusses, or because they want to watch their OS doin' nothing (many OSes have the same usefulness as this program)
162 posts
3790 posts
Lincoln, Nebraska