From: Andi Kleen <andi@firstfloor.org>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org, arjan@infradead.org,
randy.dunlap@oracle.com, rusty@rustcorp.com.au,
andi@firstfloor.org, dhowells@redhat.com,
akpm@linux-foundation.org
Subject: Re: request_module vs. modprobe blacklist (and security subsystem implications)
Date: Thu, 22 Oct 2009 02:48:10 +0200 [thread overview]
Message-ID: <20091022004810.GS32470@one.firstfloor.org> (raw)
In-Reply-To: <1256137348.4443.39.camel@dhcp231-106.rdu.redhat.com>
> The problem is that a number of programs (sendmail, procmail, sshd, and
> more) have all been seen to do operations which tried to load the ipv6
> module. These get into request_module(), hit the security hook, and are
> obviously denied since the security system doesn't see a need for those
> programs to be able to request a module be loaded.
What's the problem with being denied? After all the programs expect
this to error out
If you're worrying about the audit entries -- the obvious place
to fix that is somewhere in your security code. Don't make the rest
of the code uglier for this.
-Andi
next prev parent reply other threads:[~2009-10-22 0:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 15:02 request_module vs. modprobe blacklist (and security subsystem implications) Eric Paris
2009-10-21 19:11 ` Alan Jenkins
2009-10-21 19:27 ` Eric Paris
2009-10-21 21:00 ` Alan Jenkins
2009-10-22 5:56 ` Rusty Russell
2009-10-22 14:30 ` Eric Paris
2009-10-23 9:16 ` Rusty Russell
2009-10-23 14:23 ` Eric Paris
2009-10-23 14:59 ` Rusty Russell
2009-10-22 0:48 ` Andi Kleen [this message]
2009-10-22 1:12 ` Eric W. Biederman
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=20091022004810.GS32470@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=dhowells@redhat.com \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rusty@rustcorp.com.au \
/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