| |
| | Secure programmer: Keep an eye on inputs |
 | | If parts of your program run as "root" or some other privileged user, or have privileged access to data (such as the data in a database), then inputs to those parts from the unprivileged parts and programs are untrusted. |
 | | The privileged program, of course, must defend itself from all attacks, but this approach usually means that the part of the program that must be secured is much smaller and easier to defend. |
 | | Programs have many other inputs, such as the current directory, signals, memory maps, System V IPC, the umask, and the state of the filesystem. |
| www-106.ibm.com /developerworks/linux/library/l-sp3.html (3792 words) |
|