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: <46F94B91.5020209@hartkopp.net>
Date:	Tue, 25 Sep 2007 19:55:29 +0200
From:	Oliver Hartkopp <oliver@...tkopp.net>
To:	YOSHIFUJI Hideaki / È£ÑÀ 
	<yoshfuji@...ux-ipv6.org>
CC:	Patrick McHardy <kaber@...sh.net>,
	Urs Thuermann <urs@...ogud.escape.de>, netdev@...r.kernel.org,
	davem@...emloft.net, joe@...ches.com, tglx@...utronix.de,
	oliver.hartkopp@...kswagen.de
Subject: Re: [PATCH 5/7] CAN: Add virtual CAN netdevice driver

Patrick McHardy wrote:
> Urs Thuermann wrote:
>   
>> YOSHIFUJI Hideaki / È£ÑÀ  <yoshfuji@...ux-ipv6.org> writes:
>>
>>
>>     
>>> I'm not a lawyer, but the following lines:
>>>
>>> | + * Alternatively, provided that this notice is retained in full, this
>>>                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> | + * software may be distributed under the terms of the GNU General
>>> | + * Public License ("GPL") version 2 as distributed in the 'COPYING'
>>> | + * file from the main directory of the linux kernel source.
>>>
>>> make this whole licence imcompatible with GPL.
>>>       
>>     

The module license is "Dual BSD/GPL" as many other code in the Linux
Kernel. So this should not be any problem.


>>> I do think you need to allow people to select GPLv2 only.
>>>       
>>     

The Linux Kernel is currently under GPLv2 and we just wanted to follow
Linus' mind and so we referenced the COPYING file which many other
source does as well. Indeed it was a hard thing to make our code
available under GPL (as creating and publishing open source software is
really no a usual thing for the Volkswagen rights department). So i
discussed with the rights department about several disclaimers inside
the current Kernel (especially the stuff that has been signed off by
companies like IBM, Motorola, etc.). In this process it turned out to be
the best to license the code under "Dual BSD/GPL" as it grants more
rights to the programmer (including ourselves) than a GPL only license.
I assume this was the intention from IBM, Motorola and all the others
also. Btw. inside the Kernel context it behaves exactly like GPL code
(like all the other dual license code).

So i really can't see any problem here. If so there would have been a
big discussion about the other "Dual BSD/GPL" code.

Best regards,
Oliver

ps. I hope, i found the right words right now, as i'm not very familiar
with English :)



-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ