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] [day] [month] [year] [list]
Message-ID: <20080515182336.GB21657@elf.ucw.cz>
Date:	Thu, 15 May 2008 20:23:36 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	David Schwartz <davids@...master.com>
Cc:	pradeep singh rautela <rautelap@...il.com>, hjk@...utronix.de,
	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org
Subject: Re: [Q]Can a file be dual licensed in upstream kernel?

Hi!

> > > In my _personal_opinion_, dual licensing gives you the right to choose
> > > between two licenses.
> 
> > > Dual licensing gives every recipient both licenses from the
> > > original author.
> > > You can choose which license you will obtain rights from.
> > >
> > > > If a file is dual licensed BSD/GPLv2, anybody
> > > > (including yourself) is free to get rid of the BSD part and make it
> > > > GPLv2 only.
> 
> > > Really? Which license or law gives you the right to change the licensing
> > > terms on code you didn't write? At least in the United States,
> > > you cannot
> 
> > You don't change licensing. You got choice of two licenses, and you
> > selected one. GPL gives you right to remove the BSD licensing terms
> > you did not choose.
> 
> GPL gives you the right to remove the BSD licensing *TERMS*, but this has no
> effect on the actual license. The works do not become GPLv2 only just
> because you removed the licensing terms.

Agreed.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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