From: Adrian Bunk <bunk@fs.tum.de>
To: greg@kroah.com
Cc: linux-kernel@vger.kernel.org
Subject: [2.5 patch] SECURITY_ROOTPLUG must depend on USB
Date: Sun, 1 Jun 2003 20:44:36 +0200 [thread overview]
Message-ID: <20030601184436.GD29425@fs.tum.de> (raw)
The following patch lets SECURITY_ROOTPLUG depend on USB (otherwise
there are link errors since Root Plug Support needs
usb_bus_list{,_lock}):
--- linux-2.5.70-mm3/security/Kconfig.old 2003-06-01 20:40:40.000000000 +0200
+++ linux-2.5.70-mm3/security/Kconfig 2003-06-01 20:41:00.000000000 +0200
@@ -33,7 +33,7 @@
config SECURITY_ROOTPLUG
tristate "Root Plug Support"
- depends on SECURITY!=n
+ depends on USB && SECURITY!=n
help
This is a sample LSM module that should only be used as such.
It prevents any programs running with egid == 0 if a specific
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next reply other threads:[~2003-06-01 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 18:44 Adrian Bunk [this message]
2003-06-02 17:20 ` [2.5 patch] SECURITY_ROOTPLUG must depend on USB Greg KH
2003-06-02 21:13 ` Chris Wright
2003-06-02 21:40 ` Greg KH
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=20030601184436.GD29425@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=greg@kroah.com \
--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