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, 14 Jun 2007 12:03:35 -0700
From:	Greg KH <greg@...ah.com>
To:	Neshama Parhoti <pneshama@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Thu, Jun 14, 2007 at 09:42:16PM +0300, Neshama Parhoti wrote:
>  Forgive me for a little off-topic question but I have a difficulty
>  to understand a technical issue about this all.
> 
>  The Linux Kernel cannot easily switch licenses because of the
>  large amount of people involved in it (i.e. contributed code on which
>  they have copyright).
> 
>  But many of FSF's GNU projects are similar - for example GCC has 
>  contributors
>  from many many companies and individuals, from which I presume there
>  are who might object to GPLv3.
> 
>  So how come they can so easily move to GPLv3 ?

The FSF required copyright assignment to themselves in order to accept
the changes from the developers.  So the FSF owns the whole copyright
and can change things whenever they want, to whatever license they want.

This is the exact opposite of the kernel in which all of the original
contributors own the copyright.

Hope this helps,

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ