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]
Date:	Thu, 12 Jul 2012 19:19:03 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
Cc:	Richard Fontana <fontana2012@...il.com>,
	"Bradley M. Kuhn" <bkuhn@....org>, tytso@....edu,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 5/6] copyleft-next: remove section 7 -
 anti-tivoization

On Thu, 12 Jul 2012 10:48:44 -0700
"Luis R. Rodriguez" <mcgrof@...not-panic.com> wrote:

> From: "Luis R. Rodriguez" <mcgrof@...not-panic.com>
> 
> The anti-tivoization clauses must go if we want this license
> to be ever considered for usage with the Linux kernel.
> This patch removes that entire section.

The kernel license won't be changing anyway. It's too big a task to
figure out. Plus if you want to change license and the new license
doesn't contain protection against DRM abusers then I for one will be
withholding my permission to change it until one is added, because the
existing GPLv2 protection while unclear is there and remains to be
litigated.

Given there are people who hold the reverse true your lock detector
should have spewed ...


There are much more important things a GPL-next needs because of its use
beyond software - protection against "design right" and "design patent"
abuses. Without that the current habit of using the GPL for 3D print
designs is potentially going to end in tears.

The way to allow DRM abuse is to have a "lesser" license which allows
abuse, just as with lesser licenses for linking.

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