public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] disallow modular capabilities
Date: Sun, 2 Jan 2005 21:00:32 +0100	[thread overview]
Message-ID: <20050102200032.GA8623@lst.de> (raw)

There's been a bugtraq report about a root exploit with modular
capabilities LSM support out for more than a week.

This patch fixes it the hard way by disallowing to build the code
modular.  In fact I think allowing modular security policies is a 
really, really bad idea because loading it after boot loses far
too much state.  Would you take a patch killing the exports in
security/ ?


--- 1.10/security/Kconfig	2004-10-20 10:37:08 +02:00
+++ edited/security/Kconfig	2005-01-02 20:50:35 +01:00
@@ -54,7 +54,7 @@
 	  If you are unsure how to answer this question, answer N.
 
 config SECURITY_CAPABILITIES
-	tristate "Default Linux Capabilities"
+	bool "Default Linux Capabilities"
 	depends on SECURITY
 	help
 	  This enables the "default" Linux capabilities functionality.

             reply	other threads:[~2005-01-02 20:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-02 20:00 Christoph Hellwig [this message]
2005-01-02 20:01 ` [PATCH] disallow modular capabilities Christoph Hellwig
2005-01-02 20:28 ` Andi Kleen
2005-01-02 20:30   ` Christoph Hellwig
2005-01-02 20:47     ` Andi Kleen
2005-01-02 22:36       ` David Meybohm
2005-01-02 23:30         ` Andi Kleen
2005-01-03  0:21           ` David Meybohm
2005-01-03  0:32             ` Andi Kleen
2005-01-03 14:38               ` Florian Weimer
2005-01-03 15:52               ` Alan Cox
2005-01-04 20:24 ` Lee Revell
2005-01-04 21:05   ` Linus Torvalds
2005-01-04 21:08     ` Christoph Hellwig
2005-01-04 21:31       ` Chris Wright
2005-01-04 21:09     ` Lee Revell

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=20050102200032.GA8623@lst.de \
    --to=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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