From: "Cyril B." <cbay@excellency.fr>
To: Ian Kent <raven@themaw.net>
Cc: "autofs@vger.kernel.org" <autofs@vger.kernel.org>
Subject: Re: [PATCH] Add a --mode option to chmod the mount point of the maps
Date: Mon, 14 Sep 2015 12:12:50 +0200 [thread overview]
Message-ID: <55F69DA2.7060204@excellency.fr> (raw)
In-Reply-To: <1442223945.3030.64.camel@themaw.net>
Ian Kent wrote:
> So are you saying you don't have sufficient faith in the permissions set
> on the file systems your mounting, that contain the information you want
> to protect, that you must have the permissions of an intermediate file
> system set to ensure that information about that vulnerability is not
> seen?
I do know that there's no vulnerability at all, and that you can
trivially list users by other means.
Unfortunately, some of my less tech savvy users believe that there's a
vulnerability because they can see other accounts' home directories, and
thus feel that their own files are not safe. Is this stupid? absolutely.
But changing my /home permissions to 751 makes those users happy and
saves my time -- and my reputation as a sysadmin :)
I also do realize that the 755 permissions come from the autofs kernel
filesystem itself. But the kernel doesn't support a 'mode' option for
autofs (some other file systems do), and even if it did, autofs would
have to be patched to support it (in a slightly different way than my
current patch).
I understand that my use case may be a corner case, and I'm perfectly
fine with keeping my patch in my own tree. I figured that since I had
written the patch for myself anway, I may as well post it here as it
could be useful for others :)
Thanks!
--
Cyril B.
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
next prev parent reply other threads:[~2015-09-14 10:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-13 13:56 [PATCH] Add a --mode option to chmod the mount point of the maps Cyril B.
2015-09-14 2:31 ` Ian Kent
2015-09-14 8:42 ` Cyril B.
2015-09-14 9:20 ` Frank Thommen
2015-09-14 9:29 ` Cyril B.
2015-09-14 9:52 ` Ian Kent
2015-09-14 9:45 ` Ian Kent
2015-09-14 10:12 ` Cyril B. [this message]
2015-09-14 10:38 ` Ian Kent
2015-09-14 3:05 ` Ian Kent
2015-09-14 3:23 ` Ian Kent
2015-09-14 11:31 ` Cyril B.
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=55F69DA2.7060204@excellency.fr \
--to=cbay@excellency.fr \
--cc=autofs@vger.kernel.org \
--cc=raven@themaw.net \
/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