From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Thomas Fricaccia" <thomas_fricacci@yahoo.com>
Cc: linux-kernel@vger.kernel.org,
"Linus Torvalds" <torvalds@linux-foundation.org>,
Greg KH <greg@kroah.com>,
LSM ML <linux-security-module@vger.kernel.org>,
Crispin Cowan <crispin@crispincowan.com>
Subject: Re: LSM conversion to static interface
Date: Mon, 22 Oct 2007 18:12:20 +0100 [thread overview]
Message-ID: <20071022181220.7a9b4ab9@the-village.bc.nu> (raw)
In-Reply-To: <200710221700.l9MH0klg006152@sapphire.spiritone.com>
> The point of contention: closing LSM significantly reduces the freedom
> of an important class of Linux users, the commercial enterprises, to
> use whatever security framework they desire. Greg and Alan didn't
No it doesn't. Strange interpretations of peculiar US laws may be doing
that. Thats [with Linux community hat on] _not_our_problem_.
> Why can't a CONFIG_ system be developed that can give everyone pretty
> much what he wants? It should be possible to develop a system
> permitting much flexibility wrt security frameworks:
> 1. a kernel configured with statically-linked hooks into exactly
> one framework.
> --- OR ---
> 2. a kernel configured with an in-tree framework, but which uses
> an LSM "security_operations" table. (This is what we pretty much
> have in 2.6.23). In addition, a new boot parameter could let the
> end user name the framework to use, which would completely
> replace the in-tree default framework at boot time.
Send patches.
> In the same note, he agreed with Alan that "SarBox is not really the issue
> here." Well, I'm pretty certain that regulatory law strongly shapes
> market forces and enterprise needs. In particular, I've heard several
> times that enterprises users really want to just BUY all their security
> products, and that these products must be accompanied by documentation for
> any audits. So, I'm pretty sure that if it is "not ... the issue", it
> strongly influences the issue.
Corporations practice "liability dumping" so that would be expected. They
want to dumb liability onto their suppliers, their customers and anyone
else they can find. Its the logical commercial practice faced by any
rational body evolving in the US marketplace.
But thats still their issue, no the community's issue.
Alan
next prev parent reply other threads:[~2007-10-22 17:09 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 17:00 Thomas Fricaccia
2007-10-22 17:12 ` Alan Cox [this message]
2007-10-22 17:13 ` Greg KH
2007-10-23 5:14 ` Crispin Cowan
2007-10-23 5:32 ` david
2007-10-23 11:38 ` Simon Arlott
2007-10-23 5:53 ` Giacomo Catenazzi
2007-10-23 7:12 ` Crispin Cowan
2007-10-23 8:17 ` Giacomo A. Catenazzi
2007-10-24 3:41 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2007-10-25 11:33 Jan Engelhardt
2007-10-26 10:40 ` Samir Bellabes
2007-10-22 2:24 Thomas Fricaccia
2007-10-22 3:59 ` Greg KH
2007-10-22 17:47 ` Avi Kivity
2007-10-23 16:05 ` Adrian Bunk
2007-10-23 16:52 ` Geert Uytterhoeven
2007-10-22 10:07 ` Alan Cox
2007-10-22 16:10 ` Crispin Cowan
2007-10-22 16:50 ` Alan Cox
2007-10-22 16:56 ` Greg KH
[not found] <167451.96128.qm@web38607.mail.mud.yahoo.com>
2007-10-18 2:18 ` Linus Torvalds
2007-10-19 20:26 ` Andreas Gruenbacher
2007-10-19 20:40 ` Linus Torvalds
2007-10-20 11:05 ` Jan Engelhardt
2007-10-20 22:57 ` James Morris
2007-10-21 22:59 ` Adrian Bunk
2007-10-23 9:13 ` Jan Engelhardt
2007-10-23 5:44 ` Giacomo Catenazzi
2007-10-23 8:55 ` Jan Engelhardt
2007-10-23 9:14 ` Giacomo A. Catenazzi
2007-10-23 9:18 ` Jan Engelhardt
2007-10-23 15:20 ` Serge E. Hallyn
2007-10-23 15:28 ` Jan Engelhardt
2007-10-23 15:34 ` Serge E. Hallyn
2007-10-25 10:23 ` Valdis.Kletnieks
2007-10-19 21:07 ` James Morris
2007-10-18 1:34 Thomas Fricaccia
2007-10-18 2:03 ` Casey Schaufler
2007-10-18 2:21 ` Linus Torvalds
2007-10-18 3:06 ` Arjan van de Ven
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=20071022181220.7a9b4ab9@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=crispin@crispincowan.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=thomas_fricacci@yahoo.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®