netdev - Re: [PATCH 5/7] CAN: Add virtual CAN netdevice driver

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: <ygfir5yetfp.fsf@janus.isnogud.escape.de>
Date:	25 Sep 2007 16:00:26 +0200
From:	Urs Thuermann <urs@...ogud.escape.de>
To:	YOSHIFUJI Hideaki / È£ÑÀ 
	<yoshfuji@...ux-ipv6.org>
Cc:	netdev@...r.kernel.org, davem@...emloft.net, kaber@...sh.net,
	joe@...ches.com, tglx@...utronix.de, oliver@...tkopp.net,
	oliver.hartkopp@...kswagen.de
Subject: Re: [PATCH 5/7] CAN: Add virtual CAN netdevice driver

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.

I'm no lawyer at all, either.  And also Oliver is not, but he has
carried out the fights with our company lawyers.  Maybe he can say
something about whether we can change this.

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

The sentence you cite *does* allow distribution under GPLv2 only.  And
I think I have often read the restriction to retain such licences in
full in GPLv2 code.  Is that really incompatible?

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