linux-kernel - Re: Developing non-commercial drivers ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1227028667.12044.9.camel@skunk>
Date:	Tue, 18 Nov 2008 18:17:47 +0100
From:	Xavier Bestel <xavier.bestel@...e.fr>
To:	Fredrik Markström 
	<fredrik.markstrom@...lonenterprise.com>
Cc:	Robert Hancock <hancockr@...w.ca>, linux-kernel@...r.kernel.org
Subject: Re: Developing non-commercial drivers ?

On Tue, 2008-11-18 at 17:52 +0100, Fredrik Markström wrote:
> Thanks for the prompt respons.
> 
> I do agree that it would be better for everyone to release it under
> GPL and I have already expressed that to our customer.
> 
> At this point I feel that we have two possibilities, help our customer
> violate GPL or say no to the project. I'd prefer a third option where
> I could tell the customer that we can setup the project in a certain
> way (some "cleanroom" setup ?) to ensure that the results can not be
> considered derived work.
> 
> Is your short answer also the definite answer considering this ?

Why not distributing the driver to your client under the same licence
terms as the kernel (i.e. GPLv2, tell him you're legally tied to it),
and then let your client handle distribution to the end-user the way it
sees fit ?
That way you come out clean, and your client gets to resolve the
eventual legal troubles himself.

	Xav


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/