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:	Tue, 19 Jun 2007 22:01:00 +0200
From:	Anders Larsen <al@...rsen.net>
To:	Alexandre Oliva <aoliva@...hat.com>
Cc:	david@...g.hm, Ingo Molnar <mingo@...e.hu>,
	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>,
	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 2007-06-19 20:23:00, Alexandre Oliva wrote:
> If you take the Wikipedia definition of Tivoization, you'll see it's
> about copyleft software only, and no law mandates the use of copyleft
> software.  There's no end to bad laws, but a law that mandated the use
> of copyleft (=> free) software and at the same time prohibited
> modifications by the user would be a very contradictory one.

You're absolutely right...

Nobody forces us to use Linux in the credit-card terminals I'm currently
working on; of course we could have selected a proprietary solution (and
we would be forced to, were the Linux kernel and/or certain crucial
libraries or utilities GPLv3 only). 

Only, your statement above seems to run counter to your previous claims
that the "anti-tivoisation" provisions of GPLv3 would bring _more_
developers to copyleft software.

So which one is it?

Cheers
 Anders
-
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