mir/sudo
2
0
Fork 0
mirror of https://github.com/sudo-project/sudo.git synced 2025-08-29 05:17:54 +00:00
Code Issues Releases Wiki Activity

updated wrt /var/run/sudo

Browse Source
This commit is contained in:
Todd C. Miller 1996-03-11 01:58:02 +00:00
parent 773636c1c8
commit 21c38820f1
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
sudo.pod
View File

@ -127,14 +127,16 @@ B<sudo> executes.
For security reasons, if your OS supports shared libraries, For security reasons, if your OS supports shared libraries,
B<sudo> should always be statically linked unless the B<sudo> should always be statically linked unless the
dynamic loader disables user-defined library search paths dynamic loader disables user-defined library search paths
for setuid programs. for setuid programs. (Most modern dynamic loaders do this.)
B<sudo> will check the ownership of its timestamp directory B<sudo> will check the ownership of its timestamp directory
(F</tmp/.odus> by default) and ignore the directory's contents (F</var/run/.odus> or F</tmp/.odus> by default) and ignore
if it is not owned by root and only read, writable, and the directory's contents if it is not owned by root and
executable by root. On systems that allow users to give only read, writable, and executable by root. On systems
files away to root (via chown) it is possible for a user that allow users to give files away to root (via chown),
to create the timestamp directory before B<sudo> is run. if the timestamp directory is located in a directory writable
by anyone (ie: F</tmp>), it is possible for a user to create
the timestamp directory before B<sudo> is run.
However, because B<sudo> checks the ownership and mode of However, because B<sudo> checks the ownership and mode of
the directory, the only damage that can be done is to "hide" the directory, the only damage that can be done is to "hide"
files by putting them in the timestamp dir. This is unlikely files by putting them in the timestamp dir. This is unlikely
@ -142,7 +144,7 @@ to happen since once the timestamp dir is owned by root and
inaccessible by any other user the user placing files there inaccessible by any other user the user placing files there
would be unable to get them back out. To get around this would be unable to get them back out. To get around this
issue you can use a directory that is not world-writable issue you can use a directory that is not world-writable
for the timestamps (F</var/sudo> for instance). for the timestamps (F</var/adm/sudo> for instance).
To keep users from creating their own timestamp files To keep users from creating their own timestamp files
(by creating the timestamp directory before B<sudo> (by creating the timestamp directory before B<sudo>