[ros-kernel] User Security

Jonathan Wilson jonwil at tpgi.com.au
Fri Sep 3 08:38:07 CEST 2004


Some thoughts:
1.a bunch of "risky" events should be locked so that you need to be running 
  as admin and/or input a password before you can do them.
These include:
Adding a program to any of the "start this program at startup" lists
Loading a driver (certainly installing a driver and configuring it to load 
automatically at windows startup)
Changing various important system settings
Changing or attempting to change operating system files
And perhaps there are other "security risks"

Something else that could be done is to add a way to put a lock on a file 
or registry key such that changing it requires an admin password. Or even 
make it so that reading the file requires an admin password
and 2.some other events should be made accessable to all (unlike in real 
windows)
Specifically, the raw disk access used by games to do CD-based protection 
should be made available to non-administrators. (perhaps it could be 
limited to removable media only for non-administrators)
Also, the other things that prevent games from running in non-administrator 
accounts should be fixed in ROS so that you dont have to boot as 
administrator to run games like you do in windows.

Together, these options would make windows more secure (since you dont need 
to run administrator just to play games and stuff and also because the 
avenues used by viruses, spyware and malware to get into your system are 
locked such that if a program tries to use them, at least you get a warning.

Something like "c:\windows\temp\~1a324fed\asdrfdyter.exe" wishes to 
overwrite c:\windows\system32\kernel32.dll with 
c:\windows\temp\~1a324fed\virus.dll, if you want this to happen, enter the 
administrator password now".



More information about the Ros-kernel mailing list