- Joined
- Nov 20, 2015
- Messages
- 37,649
Currently most OS'es allow you to install software when you want it, when you need it, and to make things easier for everybody.
Unfortunately, in some cases, this can be abused, as is proved by the recent WannaCrypt outbreak (see this thread).
A long, long time ago somebody wrote an article about an OS that implements a default-deny policy, which means that if something want to run (or execute, or start up another program) it will not be able to do so unless authorized by the administrator/user of that machine. (I cannot find the original article anymore by now
)
Put in a nutshell, the policy will prohibit anything from spawning its own processes unless duly authorized.
Now I am wondering, how feasible is it to code an OS with a default-deny policy. Of course, it will also have a policy to allow you to install software (like wordprocessors, spreadsheets, web browsers, Java, or anything else that is required by the end-user).
After a successful installation, the default-deny policy is activated. Currently installed programs will be allowed to run, but if some nasty comes along and tries to spawn its own process (even through a legitimate pre-installed app), it is denied from doing its dirty tricks.
Or is it just a pipe dream?
Unfortunately, in some cases, this can be abused, as is proved by the recent WannaCrypt outbreak (see this thread).
A long, long time ago somebody wrote an article about an OS that implements a default-deny policy, which means that if something want to run (or execute, or start up another program) it will not be able to do so unless authorized by the administrator/user of that machine. (I cannot find the original article anymore by now
Put in a nutshell, the policy will prohibit anything from spawning its own processes unless duly authorized.
Now I am wondering, how feasible is it to code an OS with a default-deny policy. Of course, it will also have a policy to allow you to install software (like wordprocessors, spreadsheets, web browsers, Java, or anything else that is required by the end-user).
After a successful installation, the default-deny policy is activated. Currently installed programs will be allowed to run, but if some nasty comes along and tries to spawn its own process (even through a legitimate pre-installed app), it is denied from doing its dirty tricks.
Or is it just a pipe dream?