From: Dan Rosenberg <drosenberg@vsecurity.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, security@kernel.org
Subject: Re: [PATCH RFC] Restrictions on module loading
Date: Mon, 08 Nov 2010 07:23:36 -0500 [thread overview]
Message-ID: <1289219016.10229.14.camel@dan> (raw)
In-Reply-To: <20101108102013.0861725b@lxorguk.ukuu.org.uk>
> NAK - Its a long standing ABI.
As far as I can tell, modules_disabled was first included in 2.6.31, so
it's hardly what I'd call "long standing". However, I see your point -
it's definitely not my intention to surprise anyone by changing security
features out from under them.
I do think merging the features makes sense in this case. I'll rework
this to keep the "modules_disabled" name, where a value of "0" means
default behavior, a value of "1" means no loading or unloading (and no
changing it back), and the new value of "2" incorporates the
restrictions I'm intending to enforce.
>
> I've no objection to modules_restrict although I doubt it'll ever get
> used in the real world, but better to extend the meaning of the existing
> interface, not remove stuff.
>
There has been interest in improving the ease with which users can
enforce restrictions on automatic module loading. No one is being
forced to use it.
-Dan
next prev parent reply other threads:[~2010-11-08 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 1:23 [PATCH RFC] Restrictions on module loading Dan Rosenberg
2010-11-08 5:14 ` Kees Cook
2010-11-08 10:20 ` Alan Cox
2010-11-08 12:23 ` Dan Rosenberg [this message]
2010-11-08 13:59 ` Alan Cox
2010-11-09 5:42 ` [Security] " Eugene Teo
[not found] <fMoIy-7gR-5@gated-at.bofh.it>
2010-11-08 8:30 ` Bodo Eggert
2010-11-08 11:34 ` Andi Kleen
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=1289219016.10229.14.camel@dan \
--to=drosenberg@vsecurity.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=security@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 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.