| 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
| ||
|
Message-ID: <20070226141222.79fe37e7@lxorguk.ukuu.org.uk> Date: Mon, 26 Feb 2007 14:12:22 +0000 From: Alan <alan@...rguk.ukuu.org.uk> To: "Michael K. Edwards" <medwards.linux@...il.com> Cc: "Pavel Machek" <pavel@....cz>, davids@...master.com, "v j" <vj.linux@...il.com>, trent.waddington@...il.com, "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>, "Neil Brown" <neilb@...e.de> Subject: Re: GPL vs non-GPL device drivers > Macrovision. Just about every vendors hardware can do Macrovision. They just forget to include the Macrovision control in published code, or hide it in a tiny extra driver (Matrox) or in the BIOS switching firmware (SiS) > Just so you know I'm not making this up: I know where the "defeat > Macrovision" bits are on certain devices, and if I told you, Jack They've been published repeatedly, people have even released source code with some of the macrovision functions included. One of the DVD hardware vendors for example released complete Macrovision programming code for their DVD hardware to the public. The Nvidia driver code sets that have been investigated show no sign of either secret macrovision code or delay loops, or stuff crippling the chip. There is a reason for the last twopeople do speed limiting with hardware traces because every kiddie on the planet can do software or jumper based ones. 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