Differences between version 11 and previous revision of PerUserTempDirs.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 11 | Last edited on Tuesday, November 16, 2004 11:57:43 pm | by StuartYeates | Revert |
| Older page: | version 10 | Last edited on Tuesday, November 16, 2004 6:26:33 pm | by AristotlePagaltzis | Revert |
@@ -28,9 +28,9 @@
This means that it will remove the directory when the last shell is closed and there are no more files in the directory.
The reason for creating then deleting $TMPDIR/create.$$, as some may wonder, is to make the mkdir an atomic operation that should stop any shell that is logging out as you log in, from removing $TMPDIR before a file is created within it ($TMPDIR/.bash.$$)
-If users want scratch space to copy files between users etc, they can use /tmp directly as [LFS]
suggests, however conformant programs should use TMPDIR which now places the files in /tmp/''username'' or /tmp/''username''.''uniqueid''.
+If users want scratch space to copy files between users etc, they can use /tmp directly as LinuxFromScratch
suggests, however conformant programs should use TMPDIR which now places the files in /tmp/''username'' or /tmp/''username''.''uniqueid''.
The current flaw with this script is that it doesn't detect if /tmp/username and all the possible /tmp/username.''uniqueid''s have already been created by an attacker.
Alternatively the first script can be placed in /etc/profile.d/ and the .bash_logout script can be ignored and the directories can be removed regularly from cron if necessary.
