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:	Mon, 3 Sep 2007 02:48:00 -0700
From:	"David Schwartz" <davids@...master.com>
To:	<dhazelton@...er.net>
Cc:	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: RE: Fwd: That whole "Linux stealing our code" thing


> Mr. Floeter *CAN* request that his code be removed from said fork
> - his code
> is solely licensed (AFAICT and IIRC) under the BSD/ISC license
> and was only
> covered by the dual-license because it was integrated into a work that
> carried said dual-license. (I'm not sure how well such a revocation would
> work in reality, but it is Mr. Floeters right.)...

No. Neither the BSD license nor the GPL license permit you to revoke rights.
Mr. Floeter's code is still available under the BSD/ISC license. The BSD
license does not require you to make derived works available under a BSD
license. *His* code is still available under a BSD/ISC license, of course,
but the changed code is not.

Read the BSD license. It does not require changes to be made available under
a compatible license. This is the main difference between the BSD and GPL
licenses.

Note that it would be an error to remove the BSD license text, as the BSD
license requires you to keep it and you still need the BSD license to grant
you distribution rights to the original work. However, the license does not
apply to protectable aspects of the code not placed under the BSD license by
their original author, and it is important to add a note to that effect.

DS


-
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