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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 7 Feb 2008 15:17:41 -0800
From:	Greg KH <greg@...ah.com>
To:	Hannu Savolainen <hannu@...nsound.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	David Newall <davidn@...idnewall.com>,
	Chris Friesen <cfriesen@...tel.com>,
	Christer Weinigel <christer@...nigel.se>,
	Pekka Enberg <penberg@...helsinki.fi>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] USB: mark USB drivers as being GPL only

On Fri, Feb 08, 2008 at 12:51:22AM +0200, Hannu Savolainen wrote:
> Alan Cox kirjoitti:
>>> doesn't mean it's derived from Linux.  In the case of user-space code
>>> it's widely understood that no licence restrictions are conferred.  The
>>>     
>>
>> Actually that is also questionable. The only reason it is fairly certain
>> in Linux is Linus went to the trouble of stating that interpretation was
>> intended in the COPYING file and saying he sees it that way.
>>
>>   
>>> No.  Holders of Linux copyrights would have to prove that the
>>> proprietary code is derived from the kernel.  They have the burden of
>>> proof, and defence needs merely show that their arguments are wrong.
>>>     
>>
>> Wrong again. In civil law in the USA and most of europe the test is
>> "balance of probability".
>>   
> What is the "propability" that drivers using the interfaces now declared as 
> "EXPORT_SYMBOL_GPL" are derived from the Linux kernel source code instead 
> of some definitive documentation?
>
> As you all (should) know there is a book called "Linux Device Drivers, 3rd 
> Edition" published by O'Reilly (ISBN 0-596-00590-3)". All the USB kernel 
> interfaces are documented there. One of the authors is Greg Kroah-Hartman 
> which makes this book "definite" source of information on Linux USB driver 
> programming. I assume Greg is the author of the USB related sections.

Yes, I wrote that, and if you look at that chapter, it states it is
based on the GPL licensed documentation that comes from the kernel
itself, which was written by a lot of other people as well.

> The "legal" question is what is that which one is license the one that 
> applies? Is it the licecense of the kernel (GPL) or is it the license of 
> the documentation (no restrictions on usage)?

There is no such license on that documentation.

> The "moral" question is that why did Greg author a book that declares these 
> USB interfaces as "free to use" and soon after that made a decision that 
> they are no longer "free to use"?

Where did I ever declare these interfaces as "free to use in violation
of the GPL" anywhere?  If you look at the examples that I wrote for that
book, they are all licensed under the GPLv2 only.

Same goes for the Windows Driver book.  You can use the Windows driver
development kit and API, as long as you follow their license.  And that
license explicitly forbids using it in code that is under an open source
license.  Is describing those interfaces in a book somehow also
"immoral"?

geesh, this thread is just insane, time to just ignore it...

greg k-h
--
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/