Go to page | Previous  1 2 3
 Post subject: Re: Log files/directories in ~/tmp in 2009.1
PostPosted: Fri Nov 06, 2009 3:40 am 
   
On Thu, 5 Nov 2009, in the Usenet newsgroup alt.os.linux.mandriva, in article
, Bit Twister wrote:

Quote:
Charlie wrote:

Unless I fat fingered something somewhere I don't remember setting
these. I don't normally mess with the environment variables. It
should be a standard install. Should these point to /tmp instead
of ~/tmp?

I just booted 2009.1 and those are automagically set for you.

BACKGROUND: Security issue on a multi-user system. Someone is
getting extra paranoid about ``other'' users seeing what ``you'' have
put into /tmp/. By setting $TMP and $TMPDIR variables, temporary
files are created in those directories rather than /tmp. You may
also see this done on multi-user systems with file quotas, to make
it harder for sneaky students to stash stuff in /tmp to get around
quota limits. This also makes removing unused temp files easier
from a security standpoint.

Quote:
Just a reminder, /tmp is not going to be cleaned out unless you have
made some kind of system adjustment.

From the Linux 'Filesystem Hierarchy Standard'
(http://www.pathname.com/fhs/):

The /tmp directory must be made available for programs that require
temporary files.

Programs must not assume that any files or directories in /tmp are
preserved between invocations of the program.

Rationale: IEEE standard P1003.2 (POSIX, part 2) makes requirements
that are similar to the above section.

Although data stored in /tmp may be deleted in a site-specific
manner, it is recommended that files and directories located in
/tmp be deleted whenever the system is booted.

FHS added this recommendation on the basis of historical precedent
and common practice, but did not make it a requirement because
system administration is not within the scope of this standard.

The /var/tmp/ directory has a similar swish. Traditionally, "unused"
files (often defined as files that haven been accessed in N days) are
deleted by a cron-job ('man tmpwatch' and similar hacks), but this has
to be done carefully to avoid causing another security problem (the
job is usually run as root to be able to remove such files while not
the owner). Likewise, /tmp may be cleared at boot time (as soon as
/tmp is mounted 'rw') or (rarely) as part of the shutdown process. But
it's a ``local'' decision for the "local" administrator.

This is trading one problem (security, possibly illusionary) for
another (complexity of clearing out the stale temp files).

Old guy


 
Go to page | Previous  1 2 3





SitemapIndex SitemapIndex RSS Feed RSS Feed Channel list Channel list
 © 0x61.com 2009 - Internet Forums and much more! - All rights reserved.