mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-security-module@wirex.com, linux-kernel@vger.kernel.org
Subject: Re: Binary only module overview
Date: Wed, 26 Sep 2001 22:19:59 -0400	[thread overview]
Message-ID: <200109270219.f8R2Jxn03458@foo-bar-baz.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 27 Sep 2001 00:14:33 BST." <E15mNsv-0002Cv-00@the-village.bc.nu>
In-Reply-To: <E15mNsv-0002Cv-00@the-village.bc.nu>

On Thu, 27 Sep 2001 00:14:33 BST, Alan Cox said:
> > I'm really trying to be constructive here.  There is a real licensing 
> > problem over whether binary modules are legitimate at all, and the issue 
> > is not special to LSM. I'm trying to get LSM out of the way so that the 
> > advocates of either side can fight it out without smushing LSM in the 
> > middle :-)
> 
> Yes - I agree. The question is "can you be using the LSM module" not
> the headers - since LSM is GPL and your work relies on it 

Unfortunately, the commentary in /usr/src/linux/COPYING exempting programs
that use the syscall interface is clear as mud.

I can read it as saying "the syscall interface is hereby granted an exemption,
and other normal uses of the kernel are specifically NOT exempted".  In that
case, all authors of closed-source loadable modules are heretics and need to
be burnt at the stake. ;)

I can equally easily read it as "normal use of the kernel does not fall
under 'derivative work', and the syscall inferface is cited as one example
of normal use".  Given that Linus has been quoted elsewhere as saying that
closed-source modules are not *inherently* evil, this may be the intended reading.

I can equally easily read it as "Linus wrote it when the syscall interface WAS
the only interface, and never updated it for loadable modules...." ;)

Personally, I'd not be at all surprised to find out that none of my 3 readings
are anywhere close to the actual meaning as decided by a court of law....

				Valdis Kletnieks
				Operating Systems Analyst
				Virginia Tech

  parent reply	other threads:[~2001-09-27  2:20 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-24 20:24 Crispin Cowan
2001-09-24 23:39 ` Alan Cox
2001-09-25 23:09   ` Crispin Cowan
2001-09-25 23:15     ` jmjones
2001-09-26  3:24     ` Greg KH
2001-09-26 19:17       ` Crispin Cowan
2001-09-26 19:34         ` Alan Cox
2001-09-26 20:01         ` Greg KH
2001-09-26 22:50           ` Crispin Cowan
2001-09-26 23:14             ` Alan Cox
2001-09-27  0:22               ` Crispin Cowan
2001-09-27  2:19               ` Valdis.Kletnieks [this message]
2001-09-26 23:26             ` Greg KH
2001-09-26 20:38         ` Brian Hatch
2001-09-26 21:37         ` David Weinehall
2001-09-26 21:45           ` Ignacio Vazquez-Abrams
2001-09-26 21:58             ` Alan Cox
2001-09-26 22:09               ` Ignacio Vazquez-Abrams
2001-09-26 22:20                 ` Alan Cox
2001-09-26 23:03                   ` Ignacio Vazquez-Abrams
2001-09-26 23:46               ` Greg KH
2001-09-27 12:09                 ` Alan Cox
2001-09-27 16:49                   ` Greg KH
2001-09-28 22:50                     ` Alan Cox
2001-09-29  2:05                       ` jmjones
2001-09-29  3:37                         ` Rik van Riel
2001-09-29  3:57                           ` jmjones
2001-09-29 14:20                         ` Alan Cox
2001-09-26 22:12           ` Crispin Cowan
2001-09-26 16:36     ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2001-09-26 15:38 Giacomo Catenazzi
2001-09-26 13:08 KRAMER,STEVEN (HP-USA,ex1)
2001-09-25 22:38 Chad Hanson
2001-09-24 19:52 Petr Vandrovec
2001-09-24 18:03 ` Dave McCracken
2001-09-24 18:15   ` Eric W. Biederman
2001-09-24 16:40 Arjan van de Ven
2001-09-24 16:53 ` Rasmus Bøg Hansen
2001-09-24 16:58   ` Ignacio Vazquez-Abrams
2001-09-24 17:02   ` Andreas Steinmetz
2001-09-24 17:08   ` Anders Peter Fugmann
     [not found]     ` <Pine.LNX.4.33.0109241851281.3698-100000@grignard.amagerkollegiet .dk>
2001-09-24 17:24       ` Dave McCracken
2001-09-24 23:32   ` Alan Cox
2001-09-24 16:54 ` Alan Cox
2001-09-24 17:15 ` Kai Germaschewski
2001-09-24 17:16 ` Rick Haines
2001-09-24 17:17 ` Greg KH
2001-09-24 20:40   ` Casey Schaufler
2001-09-24 23:25     ` Alan Cox
2001-09-25 16:22       ` Casey Schaufler
2001-09-24 17:35 ` Steve Lord
2001-09-24 20:06 ` Michael Leun
2001-09-24 21:18 ` Nerijus Baliunas
2001-09-24 22:57 ` Brian Strand
2001-09-25 15:44 ` Greg KH
2001-09-25 19:09   ` Mark Zealey
2001-09-25 19:24     ` Ignacio Vazquez-Abrams
2001-09-25 20:42     ` Greg KH
2001-09-25 21:09       ` Roberto Nibali
2001-09-25 21:16         ` Greg KH
2001-09-25 22:14           ` Roberto Nibali
2001-09-25 22:15             ` Greg KH
2001-09-25 22:39               ` Roberto Nibali
2001-09-25 22:40       ` Greg KH
2001-09-26 16:38         ` Alan Cox
2001-09-25 16:43 ` Fabbione
2001-09-28  2:38   ` Edward S. Marshall
2001-09-25 23:24 ` Jes Sorensen
2001-09-28 14:09 ` Daniel Caujolle-Bert
2001-09-28 14:14   ` Arjan van de Ven
2001-09-28 14:42     ` Alan Cox
2001-09-28 14:52       ` Nicholas Knight
2001-09-29  9:04         ` Albert D. Cahalan
2001-09-28 19:44       ` Daniel Caujolle-Bert

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=200109270219.f8R2Jxn03458@foo-bar-baz.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.com \
    /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®