From: Rob Landley <rob@landley.net>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: The one and only "permission denied" in find /sys
Date: Wed, 13 Oct 2021 15:12:16 -0500 [thread overview]
Message-ID: <cd81a57e-e2c1-03c5-d0da-f898babf92e7@landley.net> (raw)
There is exactly one directory in the whole of sysfs that a normal user can't
read (at least on my stock devuan laptop):
$ find /sys -name potato
find: ‘/sys/fs/pstore’: Permission denied
It's the "pstore" filesystem, it was explicitly broken by commit d7caa33687ce,
and the commit seems to say this was to fix an issue that didn't exist yet but
might someday.
Did whatever issue it was concerned about ever actually start happening? Why did
you not change the permissions on the files _in_ the directory so they weren't
world readable instead? Should /dev/shm stop being world ls-able as well?
Confused,
Rob
next reply other threads:[~2021-10-13 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 20:12 Rob Landley [this message]
2021-10-14 1:48 ` The one and only "permission denied" in find /sys Kees Cook
2021-10-15 9:14 ` Christian Brauner
2021-10-15 21:40 ` Kees Cook
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=cd81a57e-e2c1-03c5-d0da-f898babf92e7@landley.net \
--to=rob@landley.net \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).