From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Partitions - last questions...
Date: Wed, 24 Apr 2013 12:12:46 -0400 [thread overview]
Message-ID: <5178047E.2080005@libertytrek.org> (raw)
In-Reply-To: <5177FABA.4010902@binarywings.net>
On 2013-04-24 11:31 AM, Florian Philipp <lists@binarywings.net> wrote:
> Am 24.04.2013 17:12, schrieb Tanstaafl:
>> Ok, but - does it make sense to add the noexec option to /var/tmp? Is it
>> possible that there are other apps that need exec capability in there?
> It makes sense. Any world-writable directory should be noexec to make
> script injection harder. Other directories, too, like /var/www (if you
> can, i.e. no cgi). I cannot tell you if any application might need it.
> Try it. It is easy enough to revert, maybe even with a `mount -o
> remount`, I'm not sure.
>
> Also, look at
> http://serverfault.com/questions/72356/how-useful-is-mounting-tmp-noexec
Hmmm, this only talks about /tmp... I'm talking about /var/tmp...
So, I guess you're right, I'll just need to try it and see...
>> What is the 'pass' column? Th 5th column is the 'dump' column, and the
>> 6th is the 'fsck' column, afaik?
> Okay, your "fsck" column is called "pass" in my fstab. Anyway, a value
> of two means "fsck after root", one means "fsck as root" and 0 "no
> fsck". See `man fstab`. Obviously you want fsck.
Gotcha, that's what I thought...
Thanks again Florian
next prev parent reply other threads:[~2013-04-24 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 14:44 [gentoo-user] Partitions - last questions Tanstaafl
2013-04-23 16:34 ` Florian Philipp
2013-04-23 17:59 ` Neil Bothwick
2013-04-24 10:48 ` Tanstaafl
2013-04-24 12:48 ` Florian Philipp
2013-04-24 15:12 ` Tanstaafl
2013-04-24 15:31 ` Florian Philipp
2013-04-24 16:12 ` Tanstaafl [this message]
2013-04-28 8:44 ` Florian Philipp
2013-04-24 15:39 ` Tanstaafl
2013-04-24 16:23 ` Michael Mol
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=5178047E.2080005@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--cc=gentoo-user@lists.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