linux-kernel - Re: GPL vs non-GPL device 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]

Date:	Thu, 15 Feb 2007 22:53:17 +0100
From:	Bernd Petrovitsch <bernd@...mix.at>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	Ben Nizette <ben.nizette@...et.net.au>, v j <vj.linux@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: GPL vs non-GPL device drivers

On Thu, 2007-02-15 at 18:40 +1100, Nick Piggin wrote:
> Ben Nizette wrote:
[...]
> > Question to the world here:  Distros make, as a matter of course, a 
> > series of modifications to the Linux Kernel so that their modules or 
> > features work.  What stops VJ making a patchset which effectively 
> > s/EXPORT_SYMBOL_GPL/EXPORT_SYMBOL/g 's the kernel source then 
> > distributing that under the GPL?  He then supplies his un-GPL'd modules 

Nothing. But it is pointless since that doesn't un-GPL source code.

[...]
> Rhetorical question: what stops me from taking somebody's copyrighted
> work, stripping the copyrights or falsely claiming to have a license
> to redistribute it, then selling it?

No one.
But that doesn't make the action legal or change the copyright/authors
rights in anyway (at least in the more civilized parts of the world).

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services

-
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/