public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <gentoo-user@devrieze.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] /var/tmp world rwx?
Date: Fri, 3 Jan 2003 23:50:25 +0100	[thread overview]
Message-ID: <200301032350.35573.gentoo-user@devrieze.net> (raw)
In-Reply-To: <3E1611D7.5020400@seaplace.org>

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 990 bytes --]

On Friday 03 January 2003 23:42, Kevin N. Carpenter wrote:
> I've been playing around with using tmpfs for /tmp and had it mounted
> with my standard "noexec,nodev,nosuid" anti-hack security options.  This
> works fine for VI or other normal tools.
>
> I wanted Portage to use it as well, to symbolically linked /var/tmp to
> /tmp.
>
> That broke emerge.  The "noexec" option prevents any builds from
> working.  That made me check one of my unmodified gentoo systems where I
> spotted that /var/tmp was world read/execute.  That's a security problem.
>
> Any reason that /var/tmp can't be root read/execute only?
>
> Kevin C.
>

It's a standard temporary directory so yes. It should be open for the public. 
This doesn't hold for /var/tmp/portage though. You also might want to use an 
extra tmpfs or a bind mount or a change in make.conf as emerge has some 
issues with symlinked paths.

Paul

-- 
Paul de Vrieze
Junior Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-01-03 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-03 22:42 [gentoo-dev] /var/tmp world rwx? Kevin N. Carpenter
2003-01-03 22:50 ` Paul de Vrieze [this message]
2003-01-03 23:04   ` Kevin N. Carpenter
2003-01-04  9:23 ` Sven Vermeulen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200301032350.35573.gentoo-user@devrieze.net \
    --to=gentoo-user@devrieze.net \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox