From: Adrian Bridgett <adrian@smop.co.uk>
To: linux-kernel@vger.kernel.org
Cc: Maneesh Soni <maneesh@in.ibm.com>
Subject: sysfs patches in -mm create bad permissions
Date: Mon, 9 Aug 2004 22:45:33 +0100 [thread overview]
Message-ID: <20040809214533.GA31505@smop.co.uk> (raw)
Thanks to GregKH for looking at this too.
Odd one this. It seems like whoever looks at some files in /sys first, owns
them. e.g I just created a new user fred, rebooted. Then "find /sys -user
fred" shows loads of files. Permissions are 644 and so the owner is
important.
In particular, "echo -n disk > /sys/power/state" will cause the machine to
suspend to disk (hence the security tag).
Found when I suddenly thought, "hang on, shouldn't I be root" :-)
Results so far:
2.6.8-rc2-mm1 - bad
2.6.8-rc2 - okay
2.6.8-rc3 - okay
2.6.8-rc3-mm1 - bad
.config file available on request. compiled with gcc 3.3.4 (debian 1:3.3.4-6)
Adrian
--
Email: adrian@smop.co.uk
Windows NT - Unix in beta-testing. GPG/PGP keys available on public key servers
Debian GNU/Linux -*- By professionals for professionals -*- www.debian.org
next reply other threads:[~2004-08-09 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 21:45 Adrian Bridgett [this message]
2004-08-09 22:19 ` sysfs patches in -mm create bad permissions Maneesh Soni
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=20040809214533.GA31505@smop.co.uk \
--to=adrian@smop.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
/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