From: Valdis.Kletnieks@vt.edu
To: john smith <john.smith77@gmx.net>
Cc: manfred@colorfullife.com, linux-kernel@vger.kernel.org
Subject: Re: Kernel modul licensing issues
Date: Sun, 30 Nov 2003 19:57:48 -0500 [thread overview]
Message-ID: <200312010057.hB10vm02008624@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 01 Dec 2003 01:27:58 +0100." <21620.1070238478@www5.gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
On Mon, 01 Dec 2003 01:27:58 +0100, john smith said:
> Well, the algorithm has been developped totally independent from
> linux. It also works under other OS's without any adjustments apart
> from alloc and locking stuff.
>
> The fact that it receives kernel data as input IMO does not make it
> tightly coupled to the linux kernel since the algorithm does not even
> know or care what it receives as input (at least as far as kernel data
> is concerned). It basically considers kernel data: char[]
You're probably "in the clear" if that's what's really going on, and
can probably go a route similar to NVidia (GPL interface to a binary
module). The part I'm not having warm fuzzies about is that the only
application that comes to mind that could take a char[] and be totally
kernel-independent and that would make sense in the kernel rather than
out in userspace is a crypto transform - and that's because closed
source crypto is usually not taken seriously.
Consider what Matt Blaze did to Clipper, which was even more closed
source than what you're doing.... Of course, if you're not doing
crypto, then you can apply the usual cost/benefit analysis of doing
it closed source versus the payoff for an attacker to crack it....
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2003-12-01 0:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 0:27 Kernel modul licensing issues john smith
2003-12-01 0:57 ` Valdis.Kletnieks [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-01 10:58 john smith
2003-11-30 13:23 Manfred Spraul
2003-11-30 12:30 john smith
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=200312010057.hB10vm02008624@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=john.smith77@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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).