From: Thomas Foerster <puckwork@madz.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.9-ac6
Date: Wed, 5 Sep 2001 16:36:21 +0200 [thread overview]
Message-ID: <20010905144317Z272191-760+9716@vger.kernel.org> (raw)
> christophe =?iso-8859-1?Q?barb=E9?= <christophe.barbe@lineo.fr> writes:
>>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 ?
> Congratulations, you've just invented the Microsoft HW Labs
> certification procedure with module signing. ;-)
> I can really see it:
> # insmod <module>
> This module <module> is not signed with the Linus Torvalds Hardware
> Certification Labs key.
> Do you want to
> a) insert the module anyway (Errors and Crashes from your kernel will
> not be processed by major kernel developers
> b) not insert the module
> c) search for an alternative driver that is open source, download it,
> compile it and use that instead of <module>
> d) download a skeleton driver to write your own driver
> e) install Microsoft Windows XP
> f) exit
> -> f
LOL, that's the point!
What's about : linuxupdate.linux.org
;-)
Thomas
next reply other threads:[~2001-09-05 14:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-05 14:36 Thomas Foerster [this message]
2001-09-06 19:23 ` Camiel Vanderhoeven
2001-09-06 20:14 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
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é
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 12:07 ` Alan Cox
2001-09-05 12:16 ` Arjan van de Ven
2001-09-05 12:23 ` Jan-Benedict Glaw
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=20010905144317Z272191-760+9716@vger.kernel.org \
--to=puckwork@madz.net \
--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®