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:	Fri, 15 Jun 2007 20:21:48 -0300
From:	Alexandre Oliva <aoliva@...hat.com>
To:	"Scott Preece" <sepreece@...il.com>
Cc:	"Ingo Molnar" <mingo@...e.hu>, "Rob Landley" <rob@...dley.net>,
	"Alan Cox" <alan@...rguk.ukuu.org.uk>,
	"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 Jun 15, 2007, "Scott Preece" <sepreece@...il.com> wrote:

> On 6/15/07, Alexandre Oliva <aoliva@...hat.com> wrote:
>> On Jun 15, 2007, Ingo Molnar <mingo@...e.hu> wrote:
>> 
>> > it irreversibly cuts off certain people from being to distribute
>> > GPLv3-ed software alongside with certain types of hardware that the
>> > FSF's president does not like.
>> 
>> That's not true.  They can just as well throw the key away and refrain
>> from modifying the installed software behind the users' back.

> This characterization misses something important.  For many product
> devices, like cell phones, the modification is never "behind the
> user's back"

Okay, take out the "behind the users' back", it makes no difference.
That was just to highlight the frequent evil intentions behind keeping
the keys.

I wonder if giving half the key to the user and keeping the other half
would be enough to satisfy the GPLv3 language while still enabling the
vendor and user to update the software together.

> The FSF's approval of this distinction (ROM versus replaceable) places
> the FSF's particular principles over users interests, for no
> particular reason

Over *users* interest?  How so?

> if the manufacturer believes that it cannot legally allow software
> modification, all the restriction does is force them either to make
> the software unmodifiable (which advances freedom not at all) or to
> use software under a different license (which advances freedom not
> at all).

Right.


But if the manufacturer believes that it can legally allow it, and
wants to be able to install, software modifications, then it must
decide between giving that up and letting the user do it as well.  And
this is where the users interests may prevail.

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
FSF Latin America Board Member         http://www.fsfla.org/
Red Hat Compiler Engineer   aoliva@...dhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@...d.ic.unicamp.br, gnu.org}
-
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