From: Stephen Satchell <list@fluent2.pyramid.net>
To: robw@optonline.net, David Lang <dlang@diginsite.com>
Cc: Ryan Anderson <ryan@michonline.com>,
Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: The GPL, the kernel, and everything else.
Date: Sat, 11 Jan 2003 21:12:58 -0800 [thread overview]
Message-ID: <5.2.0.9.0.20030111210824.01d30bc0@fluent2.pyramid.net> (raw)
In-Reply-To: <1042347339.1033.191.camel@RobsPC.RobertWilkens.com>
At 11:55 PM 1/11/03 -0500, Rob Wilkens wrote:
> > as for signing kernel modules as being 'good' you have a serious problem
> > in the Linux world that there is no central authority to do any such
> > signing.
>
>Microsoft uses Verisign I believe, which is a company linux commands
>like "whois" already use to do nameserver lookups for example. It's a
>third party, and hardware manufacturers probably already have
>certificates from them.
Microsoft doesn't use Verisign for its driver signing -- it's a proprietary
system that is hard-wired into Windows. I would guess you are confusing
SSL certificates with module signatures.
As for "whois" you will find the default host for the GNU version is
"whois.crsnic.net", which is not Verisign.
Microsoft signs modules that passes their test suite, and for which vendors
pay a pretty penny (five digits' worth in US Dollars, if I recall
correctly). There is no comparable central authority for Linux or GNU
software, nor would vendors be interested in spending the kind of dollars
that would be associated with that sort of certification. If they would, I
would LOVE to start such a business.
Satch
--
The human mind treats a new idea the way the body treats a strange
protein: it rejects it. -- P. Medawar
This posting is for entertainment purposes only; it is not a legal opinion.
next prev parent reply other threads:[~2003-01-12 5:04 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 15:29 Nvidia and its choice to read the GPL "differently" Larry Sendlosky
2003-01-11 1:58 ` Rob Wilkens
2003-01-11 2:07 ` Larry McVoy
2003-01-11 2:13 ` Rob Wilkens
2003-01-11 2:17 ` Larry McVoy
2003-01-11 2:38 ` Rob Wilkens
2003-01-11 2:41 ` Larry McVoy
2003-01-11 2:46 ` Rob Wilkens
2003-01-11 21:44 ` Kurt Garloff
2003-01-11 21:53 ` Rob Wilkens
2003-01-11 22:16 ` Chief Gadgeteer
2003-01-11 22:26 ` Kurt Garloff
2003-01-11 23:23 ` Rob Wilkens
2003-01-12 3:33 ` Mark Mielke
2003-01-12 3:43 ` Rob Wilkens
2003-01-12 4:19 ` David Schwartz
2003-01-13 13:51 ` Richard B. Johnson
2003-01-12 4:00 ` Valdis.Kletnieks
2003-01-12 4:04 ` Rob Wilkens
2003-01-12 7:47 ` Chuck Wolber
2003-01-12 14:42 ` Intel And Kenrel Programming (was: Nvidia is a great company) Rob Wilkens
2003-01-12 16:45 ` Alan Cox
2003-01-12 16:58 ` Rob Wilkens
2003-01-12 17:54 ` Alan Cox
2003-01-12 19:30 ` Intel And Kenrel Programming Samuli Suonpaa
2003-01-12 19:46 ` Intel And Kenrel Programming (was: Nvidia is a great company) Valdis.Kletnieks
2003-01-11 22:36 ` Nvidia and its choice to read the GPL "differently" Vojtech Pavlik
2003-01-11 22:57 ` Rob Wilkens
2003-01-12 1:06 ` The GPL, the kernel, and everything else Ryan Anderson
2003-01-12 4:15 ` Rob Wilkens
2003-01-12 4:21 ` David Lang
2003-01-12 4:55 ` Rob Wilkens
2003-01-12 5:10 ` David Lang
2003-01-12 5:45 ` Rob Wilkens
2003-01-12 5:12 ` Stephen Satchell [this message]
2003-01-16 16:28 ` Mark H. Wood
2003-01-16 16:41 ` venom
2003-01-16 18:22 ` John Alvord
2003-01-12 11:13 ` Nvidia and its choice to read the GPL "differently" Andrew McGregor
2003-01-12 1:44 ` [OT] Noise on lkml (was Re: Nvidia and its choice to read the GPL "differently") J Sloan
2003-01-12 3:18 ` Rob Wilkens
2003-01-12 4:08 ` Scott Murray
2003-01-11 3:26 ` Nvidia and its choice to read the GPL "differently" Alan Cox
2003-01-11 2:54 ` Larry McVoy
2003-01-11 2:58 ` Rob Wilkens
2003-01-11 3:11 ` Zwane Mwaikambo
2003-01-11 3:14 ` Rob Wilkens
2003-01-11 3:16 ` John Adams
2003-01-11 3:35 ` Rob Wilkens
2003-01-11 3:48 ` Hans Sgier
2003-01-11 3:55 ` Rob Wilkens
2003-01-11 4:41 ` J Sloan
2003-01-11 4:44 ` Rob Wilkens
2003-01-11 5:09 ` Andre Hedrick
2003-01-11 5:12 ` OT: Renaming the kernel??!?!?!? (Was Re: Nvidia and its choice to read the GPL "differently") Brian Davids
2003-01-11 15:57 ` Nvidia and its choice to read the GPL "differently" Tom Sightler
2003-01-11 3:27 ` Brian Tinsley
[not found] ` <1042256385.1259.106.camel@RobsPC.RobertWilkens.com>
2003-01-11 4:16 ` Brian Tinsley
2003-01-11 3:52 ` yodaiken
2003-01-11 4:05 ` Rob Wilkens
2003-01-11 5:45 ` Martin J. Bligh
2003-01-11 6:01 ` Tomas Szepe
2003-01-11 15:03 ` Rob Wilkens
2003-01-11 19:41 ` Andre Hedrick
2003-01-11 21:18 ` Rob Wilkens
2003-01-11 6:32 ` Ryan Anderson
2003-01-11 2:55 ` Rob Wilkens
2003-01-11 3:20 ` Tom Sightler
2003-01-11 19:48 ` Mark Mielke
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=5.2.0.9.0.20030111210824.01d30bc0@fluent2.pyramid.net \
--to=list@fluent2.pyramid.net \
--cc=dlang@diginsite.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robw@optonline.net \
--cc=ryan@michonline.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;
as well as URLs for NNTP newsgroup(s).