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: <2e6659dd0706201414g3a6af30cvfb50720962e9dc1c@mail.gmail.com>
Date:	Wed, 20 Jun 2007 18:14:32 -0300
From:	"Tomas Neme" <lacrymology@...il.com>
To:	"Alexandre Oliva" <aoliva@...hat.com>
Cc:	"Andrew McKay" <amckay@...rs.ca>,
	"Alan Cox" <alan@...rguk.ukuu.org.uk>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Al Viro" <viro@....linux.org.uk>,
	"Bernd Schmidt" <bernds_cb1@...nline.de>,
	"Ingo Molnar" <mingo@...e.hu>,
	"Daniel Hazelton" <dhazelton@...er.net>,
	"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

> > However, I don't see how this would ever require a company like Tivo
> > or Mastercard to have their networks play nice with a unit that has
> > been modified by the end user, potentially opening up some serious
> > security holes.
>
> Which is why the GPLv3 doesn't make the requirement that you stated.

Why, if you let user-compiled kernels to run in a TiVo, it might be
modified so the TiVo can be used to pirate-copy protected content,
which is a serious security hole. TiVo would need to read, approve of,
and sign any modified kernels the users intend to use on their
hardware. If GPLv3 allows for this, it'd be doing exactly that

Tomás

-- 
|_|0|_|
|_|_|0|
|0|0|0|
-
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