From: "christophe barbé" <christophe.barbe@lineo.fr>
To: David Schwartz <davids@webmaster.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.9-ac6
Date: Wed, 5 Sep 2001 14:50:39 +0200 [thread overview]
Message-ID: <20010905145039.A10655@pc8.lineo.fr> (raw)
In-Reply-To: <1257554973.999687013@[169.254.198.40]> <NOEJJDACGOHCKNCOGFOMAECKDLAA.davids@webmaster.com>
In-Reply-To: <NOEJJDACGOHCKNCOGFOMAECKDLAA.davids@webmaster.com>; from davids@webmaster.com on mer, sep 05, 2001 at 11:57:17 +0200
Would it not be possible with your scheme to package a closed source driver
in an open source wrapper driver and then defeat your tainting technique.
Is it legally possible to copyright a kind of magic number with a copyright
allowing only it's used in open & public source driver ?
Christophe
Le mer, 05 sep 2001 11:57:17, David Schwartz a écrit :
>
> > >> I think, perhaps, the logic should be that a module
> > >> shouldn't taint the kernel if:
>
> > >> 1) The user built the module from source on that machine, OR
>
> > >> 2) The module source is freely available without restriction
>
> > > I just realized two things. One, there's a strong argument
> that this
> > > should be an AND, not an OR.
>
> > And as all distributions would fail (1) in initial form, all
> > distributions would result in tainted kernels. Is this the
> > intent?
>
> They wouldn't taint because the kernel signature would match the
> module
> signatures. I provided more detail on one possible way this scheme would
> work and it's not quite as simple as the summary above suggests.
>
> Basically, when you compile (or install) the kernel, a random
> 'signature'
> goes in. When you compile a module, the signature goes in too. You can
> then
> compare the module's signature to the kernel's signature to ensure they
> were
> compiled as a unit. Unfortunately, this doesn't ensure that the user has
> the
> source.
>
> I suppose, if the module source were freely available, then '2'
> would
> apply. If you keep it as an OR, then distributions wouldn't taint out of
> the
> box unless they included modules whose source distribution was limited. I
> think this is what you want.
>
> DS
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
--
Christophe Barbé
Software Engineer - christophe.barbe@lineo.fr
Lineo France - Lineo High Availability Group
42-46, rue Médéric - 92110 Clichy - France
phone (33).1.41.40.02.12 - fax (33).1.41.40.02.01
http://www.lineo.com
next prev parent reply other threads:[~2001-09-05 12:50 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 1:50 Alan Cox
2001-09-03 2:51 ` Keith Owens
2001-09-03 3:08 ` Dave Jones
2001-09-03 13:05 ` Andrea Arcangeli
2001-09-03 13:21 ` Alan Cox
2001-09-05 1:51 ` Keith Owens
2001-09-05 3:30 ` David Schwartz
2001-09-05 3:50 ` Keith Owens
2001-09-05 5:16 ` David Schwartz
2001-09-05 5:39 ` Alan Shutko
2001-09-05 18:46 ` David Schwartz
2001-09-05 5:52 ` H. Peter Anvin
2001-09-05 5:56 ` Aaron Lehmann
2001-09-05 7:03 ` David Schwartz
2001-09-05 7:09 ` David Schwartz
2001-09-05 9:50 ` Alex Bligh - linux-kernel
2001-09-05 9:57 ` David Schwartz
2001-09-05 12:50 ` christophe barbé [this message]
2001-09-05 13:06 ` Alan Cox
2001-09-05 13:14 ` Alex Bligh - linux-kernel
2001-09-05 13:23 ` christophe barbé
2001-09-05 14:05 ` Henning P. Schmiedehausen
2001-09-05 7:18 ` Aaron Lehmann
2001-09-05 7:19 ` David Schwartz
2001-09-05 9:41 ` Justin Guyett
2001-09-05 9:53 ` David Schwartz
2001-09-05 10:21 ` Justin Guyett
2001-09-05 11:55 ` Alan Cox
2001-09-05 18:46 ` David Schwartz
2001-09-05 18:54 ` Alan Cox
2001-09-05 22:09 ` Linux 2.4.9-ac6 (really about tainting) David Schwartz
2001-09-05 12:07 ` Linux 2.4.9-ac6 Alan Cox
2001-09-05 12:16 ` Arjan van de Ven
2001-09-05 12:23 ` Jan-Benedict Glaw
2001-09-05 14:36 Thomas Foerster
2001-09-06 19:23 ` Camiel Vanderhoeven
2001-09-06 20:14 ` Alan Cox
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=20010905145039.A10655@pc8.lineo.fr \
--to=christophe.barbe@lineo.fr \
--cc=davids@webmaster.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
all inboxes | Powered by JetHome®