From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Vasiliy Kulikov <segoon@openwall.com>
Cc: linux-kernel@vger.kernel.org, security@kernel.org,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH] power: disable hibernation if module loading is disabled
Date: Fri, 4 Mar 2011 22:21:02 +0100 [thread overview]
Message-ID: <201103042221.02852.rjw@sisk.pl> (raw)
In-Reply-To: <20110304211035.GA28842@albatros>
On Friday, March 04, 2011, Vasiliy Kulikov wrote:
> On Fri, Mar 04, 2011 at 21:42 +0100, Rafael J. Wysocki wrote:
> > That "everyone" is actually the "full root" (in the case of /sys/power/state)
> > or someone having CAP_SYS_ADMIN in the /dev/snapshot case, right?
>
> Yes, sorry for my bad english. "Everyone" is indeed misleading :-D
>
> > Second, there's _zero_ relationship between /proc/sys/kernel/modules_disabled
> > and the hibernation interface, so please find a different way to solve the
> > problem (if there is any).
>
> If modules_disabled is set to 1, then nobody, even full root may not write
> to the kernel, right? So, if something permits to indirectly pass
> modules_disabled restriction, this is a bug. Otherwise,
> modules_disabled is confusing as it gives false sense of security.
>
> -OR-
>
> modules_disabled's documentation should be changed to note that it
> doesn't prevent rootkit uploading, but only forbids modprob'ing modules
> via the "official" init_module(2) gate, disallowing e.g. module autoloading.
Why not to change that documentation, then?
Also, please note that in order to "write" into memory using the hibernation
interface you need to have write access to swap, which you can use to corrupt
memory regardless of the modules_disabled setting AFAICS.
Thanks,
Rafael
next prev parent reply other threads:[~2011-03-04 21:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 16:11 [PATCH] power: disable hibernation if module loading is disabled Vasiliy Kulikov
2011-03-04 18:43 ` Kees Cook
2011-03-04 18:43 ` Kees Cook
2011-03-04 20:48 ` Rafael J. Wysocki
2011-03-04 20:48 ` Rafael J. Wysocki
2011-03-04 20:32 ` Pavel Machek
2011-03-04 21:52 ` Vasiliy Kulikov
2011-03-04 21:52 ` Vasiliy Kulikov
2011-03-04 20:32 ` Pavel Machek
2011-03-04 20:42 ` Rafael J. Wysocki
2011-03-04 21:10 ` Vasiliy Kulikov
2011-03-04 21:21 ` Rafael J. Wysocki [this message]
2011-03-04 21:46 ` Vasiliy Kulikov
2011-03-04 21:46 ` Vasiliy Kulikov
2011-03-04 22:30 ` Rafael J. Wysocki
2011-03-04 22:42 ` Pavel Machek
2011-03-04 22:42 ` Pavel Machek
2011-03-05 10:34 ` Vasiliy Kulikov
2011-03-05 11:24 ` Rafael J. Wysocki
2011-03-08 6:58 ` Pavel Machek
2011-03-08 6:58 ` Pavel Machek
2011-03-05 11:24 ` Rafael J. Wysocki
2011-03-05 10:34 ` Vasiliy Kulikov
2011-03-04 22:30 ` Rafael J. Wysocki
2011-03-04 21:21 ` Rafael J. Wysocki
2011-03-04 21:10 ` Vasiliy Kulikov
2011-03-04 20:42 ` Rafael J. Wysocki
2011-03-04 21:27 ` [Security] " Greg KH
2011-03-04 21:51 ` Vasiliy Kulikov
2011-03-04 21:51 ` Vasiliy Kulikov
2011-03-04 21:27 ` Greg KH
2011-03-06 19:36 ` david
2011-03-06 19:36 ` david
-- strict thread matches above, loose matches on Subject: below --
2011-03-04 16:11 Vasiliy Kulikov
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=201103042221.02852.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--cc=security@kernel.org \
--cc=segoon@openwall.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.