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: <20070619215615.ef6d7aad.diegocg@gmail.com>
Date:	Tue, 19 Jun 2007 21:56:15 +0200
From:	Diego Calleja <diegocg@...il.com>
To:	Nicolas Mailhot <nicolas.mailhot@...oste.net>
Cc:	davids@...master.com, linux-kernel@...r.kernel.org
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

El Tue, 19 Jun 2007 20:21:53 +0200, Nicolas Mailhot <nicolas.mailhot@...oste.net> escribió:

> traffic regulations only consider cars? I think not. Yet the same
> argument is the core of most GPL v3 objections we've seen in this
> thread.

No, the core argument of the GPLv3 objections is that you can NOT tell the
hardware manufacturers how to build hardware. You only  can tell software
users what hardware (tivoized) it's forbidden for them. Wether or not the
hardware manufacturers are going to care enought about your anti-tivo
software to remove their tivo protections is a completely different question
unrelated to the software license. Which is why the GPLv3 anti-tivoization
measures are stupid and pointless. 

Please, stop pretending you are hardware manufacturers. You are not.
-
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