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:	Sun, 17 Jun 2007 21:18:53 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Alexandre Oliva <aoliva@...hat.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Daniel Hazelton <dhazelton@...er.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Greg KH <greg@...ah.com>,
	debian developer <debiandev@...il.com>, david@...g.hm,
	Tarkan Erimer <tarkan@...one.net.tr>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

On Sun, 17 Jun 2007 15:33:33 -0300
Alexandre Oliva <aoliva@...hat.com> wrote:

> On Jun 17, 2007, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> 
> >> I don't know any law that requires tivoization.
> 
> > In the USSA it is arguable that wireless might need it (if done in
> > software) for certain properties. (The argument being it must be
> > tamperproof to random end consumers).
> 
> But this is not tivoization.

It most definitely is

> Tivoization is a manufacturer using technical measures to prevent the
> user from tampering (*) with the device, *while* keeping the ability
> to tamper with it changes itself.

That accurately describes the FCC wireless rules. As a vendor I am
perfectly allowed to tinker, but the product must not be "end user"
modifiable. (and some vendors take this to mean binary only, despite the
fact end users generally aren't able to modify code and EE students are
just as able to modify electronics as we are code).

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