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:	Wed, 20 Jun 2007 14:16:57 -0700 (PDT)
From:	david@...g.hm
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>,
	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 Wed, 20 Jun 2007, Alexandre Oliva wrote:

> Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
> 
> On Jun 20, 2007, Andrew McKay <amckay@...rs.ca> wrote:
>
>> 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.

so if the BIOS checked the checksum of the boot image and if it found it 
wasn't correct would disable the video input hardware but let you boot the 
system otherwise it would be acceptable to you and the GPLv3?

somehow I doubt it, but that's what it would take to prevent modified 
software from interacting with their networks (remembering that these 
networks are the cable and satellite networks in some cases)

it also seems that if this was the case it would be a trivial work-around 
for the GPLv3 if it was acceptable.

David Lang
-
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