1 {{short description|Practice of a hardware developer making only a specific version of free software runnable}}
2 {{Use mdy dates|date=January 2023}}
4 '''Tivoization''' {{IPAc-en|ˈ|t|iː|v|oʊ|ᵻ|ˌ|z|eɪ|ʃ|ən}} is the practice of designing hardware that incorporates [[software]] under the terms of a [[copyleft]] [[software license]] like the [[GNU General Public License]] (GNU GPL), but uses [[hardware restriction]]s or [[digital rights management]] (DRM) to prevent users from running modified versions of the software on that hardware. [[Richard Stallman]] coined the term in reference to [[TiVo]]'s use of GNU GPL licensed software on the TiVo brand [[digital video recorder]]s (DVR), which actively blocks users from running modified software on its hardware by design.<ref>{{cite web |url=https://www.gnu.org/licenses/gpl-faq.html#Tivoization |title=Frequently Asked Questions about the GNU Licenses |access-date=March 17, 2015 |url-status=live |archive-url=https://web.archive.org/web/20161229211715/https://www.gnu.org/licenses/gpl-faq.html |archive-date=December 29, 2016}} GNU.org Frequently Asked Questions about the GNU Licenses</ref><ref>{{cite web |url=https://www.gnu.org/licenses/quick-guide-gplv3.html |title=A Quick Guide to GPLv3 |access-date=March 17, 2015 |url-status=live |archive-url=https://web.archive.org/web/20161229211618/https://www.gnu.org/licenses/quick-guide-gplv3.html |archive-date=December 29, 2016}} A Quick Guide to GPLv3</ref> Stallman believes this practice denies users some of the freedom that the GNU GPL was designed to protect.<ref>{{cite web |url=http://gplv3.fsf.org/pipermail/info-gplv3/2006-February/000001.html |archive-url=https://web.archive.org/web/20061026084218/http://gplv3.fsf.org/pipermail/info-gplv3/2006-February/000001.html |url-status=dead |archive-date=October 26, 2006 |title=[Info-gplv3] GPLv3 Update #2 |work=fsf.org |access-date=October 2, 2015}}</ref> The [[Free Software Foundation]] refers to tivoized hardware as "tyrant devices".<ref name="tyrants">{{cite web |url=http://www.gnu.org/proprietary/proprietary-tyrants.html |title=Proprietary Tyrants |publisher=Free Software Foundation |access-date=January 28, 2023|archive-url=https://web.archive.org/web/20150924024955/http://www.gnu.org/proprietary/proprietary-tyrants.html |archive-date=September 24, 2015 |url-status=live}}</ref>
7 TiVo's software incorporates the [[Linux kernel]] and [[GNU]] software, both of which are licensed under version 2 of the [[GNU General Public License]] (GPLv2). GPLv2 requires distributors to make the corresponding [[source code]] available to each person who receives the software. The goal of this requirement is to allow users of GPL-covered software to modify the software to better suit their purposes.<ref>{{cite web |url=https://www.gnu.org/philosophy/free-sw.html |title=The Free Software Definition |quote=...The freedom to study how the program works, and adapt it to your needs... | access-date=January 28, 2023 |archive-url=https://web.archive.org/web/20230127163705/https://www.gnu.org/philosophy/free-sw.html |archive-date=January 27, 2023 |url-status=live}}</ref>
9 However, Stallman asserts that TiVo circumvented this goal by making their products run programs only if the program's [[digital signature]] matches those authorized by the manufacturer of the TiVo.<ref>{{cite web |url=http://www.gratisoft.us/tivo/bigdisk.html |title=Using large disks with TiVo |work=gratisoft.us |access-date=October 2, 2015 |archive-url=https://web.archive.org/web/20120206023943/http://www.gratisoft.us/tivo/bigdisk.html |archive-date=February 6, 2012 |url-status=dead}}</ref> While TiVo has complied with the GPL v2 requirement to release the source code for others to modify, any modified software will not run on TiVo's hardware.
11 [[Linus Torvalds]], the original author of the Linux kernel, supported the use of DRM in response.<ref>{{cite web |url=https://groups.google.com/g/fa.linux.kernel/c/L5NRD_ONkIk/m/Vps_c1wLyiQJ |title=fa.linux.kernel: Linus Torvalds: Flame Linus to a crisp! |date=April 24, 2003 |work=google.com |access-date=December 27, 2020 |archive-url=https://web.archive.org/web/20201227002332/https://groups.google.com/g/fa.linux.kernel/c/L5NRD_ONkIk |archive-date=December 27, 2020 |url-status=live}}</ref> Other Linux developers, including [[Alan Cox (computer programmer)|Alan Cox]], have expressed divergent opinions.<ref>{{cite web |url=http://news.zdnet.co.uk/software/0,1000000121,39249913,00.htm |archive-url=https://web.archive.org/web/20090428180852/http://news.zdnet.co.uk/software/0,1000000121,39249913,00.htm |title=UK Linux guru backs GPL 3 |work=ZDNet |date=January 31, 2006 |access-date=October 2, 2015 |archive-date=April 28, 2009 |url-status=dead}}</ref>
13 Stallman and the Free Software Foundation attempted to respond to some of these concerns. They have stated that their goal is for GPLv3 to allow private digital signatures for security purposes, but to still prevent tivoization.<ref>{{cite web | url=https://lkml.org/lkml/2007/6/13/289 | title=LKML: Linus Torvalds: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |access-date=January 28, 2023 |archive-url=https://web.archive.org/web/20070617234347/http://lkml.org/lkml/2007/6/13/289 |archive-date=June 17, 2007 |url-status=live}}</ref>
16 In 2006, the [[Free Software Foundation]] (FSF) decided to combat TiVo's technical system of blocking users from running modified software. The FSF subsequently developed a new version of the [[GNU General Public License#Version 3|GNU General Public License (Version 3)]] which was designed to include language which prohibited this activity.<ref>{{cite web |url=https://fsfe.org/activities/gplv3/brussels-rms-transcript#tivoisation |title=Richard Stallman explains the new GPL provisions to block "tivoisation" | access-date=January 28, 2023 | archive-url=https://web.archive.org/web/20221006035111/https://fsfe.org/activities/gplv3/brussels-rms-transcript#tivoisation |archive-date=October 6, 2022 |url-status=live}}</ref>
18 The [[Linux kernel]], which is included in the [[operating system]] of TiVo-branded hardware, is distributed under the terms of the GPLv2. The FSF's goal is to ensure that all recipients of software licensed under the GPLv3 are not restricted by hardware constraints on the modification of distributed software.
20 This new license provision was acknowledged by TiVo in its April 2007 [[SEC filing]]: "we may be unable to incorporate future enhancements to the GNU/Linux operating system into our software, which could adversely affect our business".<ref>{{cite web |url=https://www.informationweek.com/software/tivo-warns-investors-new-open-source-license-could-hurt-business |title=InformationWeek: TiVo Warns Investors New Open Source License Could Hurt Business|date=June 1, 2007 |archive-url=https://web.archive.org/web/20220727084236/https://www.informationweek.com/software/tivo-warns-investors-new-open-source-license-could-hurt-business |archive-date=July 27, 2022 |url-status=live}}</ref> The [[Linux kernel]] has not been changed to use GPLv3 due to certain problems perceived by its maintainers.<ref name="linuxlicense">{{cite web |url=https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/COPYING?id=b3358a116c25267446a45e4164cb2b8e98276da0 |quote=''Also note that the only valid version of the GPL as far as the kernel is concerned is _this_ particular version of the license (ie v2, not v2.2 or v3.x or whatever), unless explicitly otherwise stated.'' |access-date=August 13, 2013 |publisher=kernel.org |first=Linus |last=Torvalds |title=COPYING |id=blob ca442d313d86dc67e0a2e5d584b465bd382cbf5c |archive-url=https://web.archive.org/web/20230128083313/https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/COPYING?id=b3358a116c25267446a45e4164cb2b8e98276da0 |archive-date=January 28, 2023 |url-status=live }}</ref><ref>{{cite web |url=https://lwn.net/Articles/200422/ |title=Kernel developers' position on GPLv3 – The Dangers and Problems with GPLv3 |first1=James E.J. |last1=Bottomley |first2=Mauro Carvalho |last2=Chehab |first3=Thomas |last3=Gleixner |first4=Christoph |last4=Hellwig |first5=Dave |last5=Jones |first6=Greg |last6=Kroah-Hartman |first7=Tony |last7=Luck |first8=Andrew |last8=Morton |first9=Trond |last9=Myklebust |first10=David |last10=Woodhouse |date=September 15, 2006 |publisher=[[LWN.net]] |access-date=March 11, 2015 |quote="The current version (Discussion Draft 2) of GPLv3 on first reading fails the necessity test of section 1 on the grounds that there's no substantial and identified problem with GPLv2 that it is trying to solve. However, a deeper reading reveals several other problems with the current FSF draft: 5.1 DRM Clauses [...] 5.2 Additional Restrictions Clause [...] 5.3 Patents Provisions [...]since the FSF is proposing to shift all of its projects to GPLv3 and apply pressure to every other GPL licensed project to move, we foresee the release of GPLv3 portends the [[Balkanisation]] of the entire Open Source Universe upon which we rely." |archive-url=https://web.archive.org/web/20060925172439/http://lwn.net/Articles/200422/ |archive-date=September 25, 2006 |url-status=live}}</ref><ref>{{cite AV media | url=https://www.youtube.com/watch?v=PaKIZ7gJlRU |title=Linus Torvalds says GPL v3 violates everything that GPLv2 stood for |date=September 4, 2014 |access-date=March 11, 2015 |archive-url=https://web.archive.org/web/20161119072821/https://www.youtube.com/watch?v=PaKIZ7gJlRU |archive-date=November 19, 2016 |url-status=live |work= [[Debconf]] 2014 |location=Portland}}</ref>
23 One of the goals of [[GNU General Public License Version 3]] is to prevent tivoization. According to [[Eben Moglen]], "the license should prohibit technical means of evasion of its rules, with the same clarity that it prohibits legal evasion of its rules."<ref>{{cite web |url=https://fsfe.org/activities/gplv3/barcelona-moglen-transcript.en.html#drm |title=Eben Moglen, speaking about GPLv3 in Barcelona |access-date=January 28, 2023 | archive-url=https://web.archive.org/web/20230112031229/https://fsfe.org/activities/gplv3/barcelona-moglen-transcript.en.html#drm | archive-date=January 12, 2023 | url-status=live}}</ref>
25 The second draft of the GPLv3 attempted to clarify this.<ref>{{cite web |url=http://gplv3.fsf.org/drm-dd2.html |title=Opinion on Digital Restrictions Management |work=fsf.org |access-date=October 2, 2015 |archive-url=https://web.archive.org/web/20060819170543/http://gplv3.fsf.org/drm-dd2.html |archive-date=August 19, 2006 | url-status=live}}</ref> However, some Linux kernel developers were still concerned that this draft may still prohibit beneficial uses of digital signatures.<ref>{{cite web |url=http://groups.google.com/group/linux.kernel/msg/36ad030397f575f5 |title=GPLv3 Position Statement |date=September 22, 2006 |first1=James E.J. |last1=Bottomley |first2=Mauro Carvalho |last2=Chehab |first3=Thomas |last3=Gleixner |first4=Christoph |last4=Hellwig |first5=Dave |last5=Jones |first6=Greg |last6=Kroah-Hartman |first7=Tony |last7=Luck |first8=Andrew |last8=Morton |first9=Trond |last9=Myklebust |first10=David |last10=Woodhouse |work=google.com |access-date=October 2, 2015 |archive-url=https://web.archive.org/web/20211202200652/https://groups.google.com/g/linux.kernel/c/IdRykVVBrEg/m/9XX1lwMDrTYJ |archive-date=December 2, 2021 | url-status=live}}</ref>
27 In the third and fourth discussion drafts of the GPLv3, released 28 March 2007 and 31 May 2007 respectively, the anti-tivoization clause was limited so as not to apply when the software is distributed to a business.<ref>{{cite web |author=brett |url=http://gplv3.fsf.org/dd3-faq |title=GPLv3 FAQ, with explanation of Section 6's limits | |date=2007-06-26 |access-date=January 28, 2023 |archive-url=https://web.archive.org/web/20070606082643/http://gplv3.fsf.org/dd3-faq |archive-date=June 6, 2007 |url-status=live}}</ref> Thus, medical devices and voting machines would not be covered. The final, official GPLv3 was published on 29 June 2007 with no major changes in respect to tivoization relative to the fourth draft.
29 [[Linus Torvalds]] said he was "pretty pleased" with the new draft's stance on [[Digital Rights Management|DRM]].<ref>{{cite web |url=http://news.com/2061-10795_3-6171300.html |title=Torvalds 'pretty pleased' about new GPL 3 draft |publisher=CNet news.com |archive-url=https://archive.today/20120713115859/http://news.cnet.com/8301-10784_3-6171300-7.html |archive-date=July 13, 2012}}</ref> However, he still does not support [[Software relicensing|relicensing]] the Linux kernel under GPLv3, stating that:<ref>{{cite web |url=https://lkml.org/lkml/2007/6/13/289 |first=Linus |last=Torvalds |title=Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |work=Linux Kernel Mailing List |date=June 13, 2007 |access-date=January 28, 2023 |archive-url=https://web.archive.org/web/20070617234347/http://lkml.org/lkml/2007/6/13/289 |archive-date=June 17, 2007 |url-status=live}}</ref>
31 {{quote|[[Richard Stallman|Stallman]] calls it "tivoization", but that's a word he has made up, and a term I find offensive, so I don't choose to use it. It's offensive because Tivo never did anything wrong, and the FSF even acknowledged that. The fact [is] that they do their hardware and have some DRM issues with the content producers and thus want to protect the integrity of that hardware.
33 The kernel license covers the *kernel*. It does not cover boot loaders and hardware, and as far as I'm concerned, people who make their own hardware can design them any which way they want. Whether that means "booting only a specific kernel" or "sharks with lasers", I don't care.}}
35 In any case, offering the Linux kernel under a different license would likely be infeasible because of its very large number of copyright holders. Unlike most GPL software, the kernel is licensed only under GPLv2 without the wording "or, at
36 your option, any later version", therefore the explicit agreement of all copyright holders would be required to license it under a new version.<ref>{{cite web |url=http://blogs.fsfe.org/ciaran/?p=58 |title=(About GPLv3) Can the Linux Kernel Relicense? — Ciarán's free software notes |author=Mark P. Lindhout |date=October 16, 2006 |work=fsfe.org |access-date=October 2, 2015 |archive-url=https://web.archive.org/web/20090223105632/http://blogs.fsfe.org/ciaran/?p=58 |archive-date=Feb 23, 2009 |url-status=live}}</ref>
38 Some other projects widely used in tivoized embedded systems, such as [[BusyBox]], have also declined to move to GPLv3.<ref>{{cite web |title=Busy busy busybox |url=https://lwn.net/Articles/202106/ |work=LWN |access-date=January 28, 2023 |archive-url=https://web.archive.org/web/20061105234312/http://lwn.net/Articles/202106/ |archive-date=November 5, 2006 |url-status=live}}</ref>
40 The [[Creative Commons license]]s also have anti-DRM clauses.<ref>{{cite web | url=https://creativecommons.org/faq/#can-i-use-effective-technological-measures-such-as-drm-when-i-share-cc-licensed-material | title=Frequently Asked Questions - Creative Commons |date=January 13, 2023 |access-date=January 28, 2023 |archive-url=https://web.archive.org/web/20230128072926/https://creativecommons.org/faq/#can-i-use-effective-technological-measures-such-as-drm-when-i-share-cc-licensed-material |archive-date=January 28, 2023 |url-status=live}}</ref>
44 * [[Defective by Design]]
51 *[https://www.gnu.org/licenses/gpl-faq.html#Tivoization Free Software Foundation definition of "Tivoization"]
52 *[http://www.linfo.org/tivoization.html An Introduction to Tivoization] by The Linux Information Project (LINFO)
53 *[http://www.mail-archive.com/blinuxforum@lists.freearchive.org/msg00592.html Stallman, Torvalds, Moglen share views on DRM and GPLv3] – by Shashank Sharma August 9, 2006, from [[Newsforge]]
54 *[http://www.tivo.com/linux/ TiVo's GPL-required modifications] to the [[Linux kernel]], [[glibc]], and other software
55 *Richard Stallman's explanations of "tivoisation":
56 **[https://fsfe.org/activities/gplv3/torino-rms-transcript.en.html#drm Italy, March 2006]
57 **[https://fsfe.org/activities/gplv3/fisl-rms-transcript.en.html#tivoisation Brazil, April 2006]
58 **[https://fsfe.org/activities/gplv3/barcelona-rms-transcript.en.html#tivoisation Spain, June 2006]
59 **[https://fsfe.org/activities/gplv3/bangalore-rms-transcript.en.html#tivoisation India, August 2006]
60 **[https://fsfe.org/activities/gplv3/tokyo-rms-transcript#tivoisation Japan, November 2006]
61 **[[commons:Category:Richard Stallman and Bruce Perens at Hi! Tech Festival|Stallman and Bruce Perens debating about GPL and tivoization (on Wikimedia Commons)]]{{dead link|date=December 2015}}
62 *[[Eben Moglen]]'s explanations:
63 **[https://fsfe.org/activities/gplv3/barcelona-moglen-transcript.en.html#drm Spain, June 2006]
64 *Ciarán O'Riordan's explanations:
65 **[https://fsfe.org/activities/gplv3/tokyo-ciaran-transcript#tivoisation-and-freedom Japan, November 2006]
66 **[http://fsfe.org/en/fellows/ciaran/ciaran_s_free_software_notes/tivoisation_explained_implementation_and_harms Tivoisation explained – implementation and harms] (article)
67 *{{cite web |url=http://linuxdevices.com/articles/AT3899346728.html |title="Using a hypervisor to reconcile GPL and proprietary embedded code" article |access-date=August 30, 2007 |archive-url=https://archive.today/20130104020016/http://linuxdevices.com/articles/AT3899346728.html |archive-date=January 4, 2013 |url-status=dead}} with a focus on Tivoization
72 [[Category:Free software culture and documents]]
73 [[Category:Technology neologisms]]
projects / BK-2020-09.git / blob