linux-kernel - Re: [PATCH] USB: mark USB drivers as being GPL only

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 7 Feb 2008 17:13:22 +0100
From:	Hans-Jürgen Koch <hjk@...utronix.de>
To:	David Newall <davidn@...idnewall.com>
Cc:	Christer Weinigel <christer@...nigel.se>,
	Marcel Holtmann <marcel@...tmann.org>,
	Diego Zuccato <diego@...llo.alma.unibo.it>,
	Greg KH <greg@...ah.com>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] USB: mark USB drivers as being GPL only

Am Fri, 08 Feb 2008 01:01:24 +1030
schrieb David Newall <davidn@...idnewall.com>:

> > It is not legally meaningless if copyright holders publicly state
> > how they interpret the license and what they consider a license
> > violation. 
> 
> Copyright-holders' opinions mean nothing.  In the particular case of
> EXPORT_SYMBOL_GPL, copyright-holders' opinions are clearly flawed
> because they make a statement about code that they do not even know
> of. 

What are you talking about? That's what every GPL-licensed library
does. By putting a library under the GPL, the copyright-holder clearly
states that he considers all programs that link against that library a
derived work. And that he therefor requires these programs to be GPL,
too, no matter if these programs already exist or not.

The LGPL exists to allow the linked program to be non-GPL, remember?
But the kernel is GPL, and not LGPL. And all these arguments that a
kernel module does not "link" against the kernel code, is therefor not
a derived work, and not bound by the GPL's restrictions, is just
artificial nonsense.

> It's equivalent to someone saying, "you are wrong," before you've
> even thought about saying something.

No. The GPL is about derived work. Derived code can obviously only
appear _after_ the original work.

> 
> > In the end, a court must decide, but lots of courts will at least
> > look at the statements the copyright holders made over the years.
> >
> >   
> >> and politically damaging.
> >>     
> >
> > That's your opinion because it's damaging _your_ political goals.
> >   
> 
> How ludicrous.  That's as much a nonsense as EXPORT_SYMBOL_GPL.  You
> have no idea what my political goals are.
> 
> Less there be further confusion: I am not an advocate for binary
> drivers.  

Nice to hear. So, if you're an advocate for open source drivers, why do
you have problems making them GPL?

> That role is reserved for others.  However that does not
> stop me from criticising something that is obviously wrong.  Stating
> that only a GPL code is permitted to use a symbol contravenes the GPL,
> because the GPL states no such requirement.  Saying that it's
> impossible for code that uses the symbol to be non-GPL (as has been
> claimed) is a lie at worst, and a hope at best.  Nobody claiming such
> a thing could know it to be true.  (It is not true.)

Using a symbol from a library means linking to it, and that creates a
derived work. Why should it be different when using kernel symbols?

Thanks,
Hans

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