linux-kernel - Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 15 Jun 2007 17:03:07 -0500
From:	"Scott Preece" <sepreece@...il.com>
To:	"Alexandre Oliva" <aoliva@...hat.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 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", but is done because the user has requested it (to fix a
problem or add a new feature). If you go to ROM-based software, the
user loses, because problems can't be fixed. For certain kinds of
problems the user might be able to get a replacement device, but
potentially involving losing any data stored on the device.

The FSF's approval of this distinction (ROM versus replaceable) places
the FSF's particular principles over users interests, for no
particular reason - 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). The result? The user STILL has no
freedom to modify the software and the community around the software
is diminished.

To go back to the "behind your back" claim, the only cases I know
where the software is replaced behind the users' back are cases were
the updates are done by a service (usually not operated by the device
manufacturer) that the user has voluntarily requested (like TiVo
program guides or cable system subscriptions), which is generally a
cases outside the scope of the license in any case.

scott
-
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/