[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/server/staging/proprietary/rec mobiles-stub...
|
From: |
Therese Godefroy |
|
Subject: |
www/server/staging/proprietary/rec mobiles-stub... |
|
Date: |
Sun, 16 Sep 2018 06:09:28 -0400 (EDT) |
CVSROOT: /webcvs/www
Module name: www
Changes by: Therese Godefroy <th_g> 18/09/16 06:09:28
Added files:
server/staging/proprietary/rec: mobiles-stub.html
Removed files:
server/staging/proprietary/rec: mobile-stub.html
Log message:
mobile-stub.html renamed to mobiles-stub.html.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/staging/proprietary/rec/mobiles-stub.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/staging/proprietary/rec/mobile-stub.html?cvsroot=www&r1=1.1&r2=0
Patches:
Index: mobiles-stub.html
===================================================================
RCS file: mobiles-stub.html
diff -N mobiles-stub.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ mobiles-stub.html 16 Sep 2018 10:09:28 -0000 1.1
@@ -0,0 +1,193 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.85 -->
+<title>Malware in Mobile Devices
+- GNU Project - Free Software Foundation</title>
+<style type="text/css" media="print,screen"><!--
+li dl { margin-top: .3em; }
+li dl dt { margin: .3em 0 0 0; font-weight: normal; font-style: italic; }
+li dl dd { margin: 0 3%; }
+--></style>
+<!--#include virtual="/proprietary/po/malware-mobiles.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Malware in Mobile Devices</h2>
+
+<p><a href="/proprietary/proprietary.html">Other examples of proprietary
+malware</a></p>
+
+<div class="highlight-para">
+<p>
+<em>Malware</em> means software designed to function in ways that
+mistreat or harm the user. (This does not include accidental errors.)
+</p>
+
+<p>
+Malware and nonfree software are two different issues. The difference
+between <a href="/philosophy/free-sw.html">free software</a> and
+nonfree software is in <a
+href="/philosophy/free-software-even-more-important.html">
+whether the users have control of the program or vice versa</a>. It's
+not directly a question of what the program <em>does</em> when it
+runs. However, in practice nonfree software is often malware, because
+the developer's awareness that the users would be powerless to fix any
+malicious functionalities tempts the developer to impose some.
+</p>
+
+<p>Nearly all mobile phones do two grievous wrongs to their users:
+tracking their movements, and listening to their conversations. This
+is why we call them “Stalin's dream”.</p>
+
+<p>If you know of an example that ought to be in this page but isn't
+here, please write
+to <a href="mailto:address@hidden";><address@hidden></a>
+to inform us. Please include the URL of a trustworthy reference or two
+to present the specifics.</p>
+</div>
+
+<ul>
+ <li><p>The phone network
+ <a href="https://ssd.eff.org/en/module/problem-mobile-phones";>
+ tracks the movements of each phone</a>.</p>
+ <p>This is inherent in the design of the phone network: as long as
+ the phone is in communication with the network, there is no way
+ to stop the network from recording its location. Many countries
+ (including the US and the EU) require the network to store all
+ these location data for months or years.</p>
+ </li>
+ <li><p id="universal-back-door">Almost every phone's communication processor
has
+ a universal back door which
+ is <a
href="https://www.schneier.com/blog/archives/2006/12/remotely_eavesd_1.html";>
+ often used to make a phone transmit all conversations it
+ hears</a>.</p>
+ <p>The back
+ door <a
href="http://www.osnews.com/story/27416/The_second_operating_system_hiding_in_every_mobile_phone";>
+ may take the form of bugs that have gone 20 years unfixed</a>.
+ The choice to leave the security holes in place is morally
+ equivalent to writing a back door.</p>
+ <p>The back door is in the “modem processor”, whose
+ job is to communicate with the radio network. In most phones,
+ the modem processor controls the microphone. In most phones it
+ has the power to rewrite the software for the main processor
+ too.</p>
+ <p>A few phone models are specially designed so that the modem
+ processor does not control the microphone, and so that it can't
+ change the software in the main processor. They still have the
+ back door, but at least it is unable to turn the phone unto a
+ listening device.</p>
+ <p>The universal back door is apparently also used to make phones
+ <a
href="http://www.slate.com/blogs/future_tense/2013/07/22/nsa_can_reportedly_track_cellphones_even_when_they_re_turned_off.html";>
+ transmit even when they are turned off</a>. This means their movements
+ are tracked, and may also make the listening feature work.</p>
+ </li>
+</ul>
+
+<p>Here are examples of malware in mobile devices. See also
+the <a href="/proprietary/malware-apple.html">the Apple malware
+page</a> for malicious functionalities specific to the Apple iThings.</p>
+
+<div class="summary" style="margin-top: 1em">
+<h3>Type of malware</h3>
+<ul>
+<li><a href="#back-doors">Back doors</a></li>
+<!--<li><a href="#censorship">Censorship</a></li>-->
+<li><a href="#insecurity">Insecurity</a></li>
+<!--<li><a href="#sabotage">Sabotage</a></li>-->
+<!--<li><a href="#interference">Interference</a></li>-->
+<li><a href="#surveillance">Surveillance</a></li>
+<li><a href="#drm">Digital restrictions
+ management</a> or “DRM” means functionalities designed
+ to restrict what users can do with the data in their computers.</li>
+<li><a href="#jails">Jails</a>—systems
+ that impose censorship on application programs.</li>
+<li><a href="#tyrants">Tyrants</a>—systems
+ that reject any operating system not “authorized” by the
+ manufacturer.</li>
+</ul>
+</div>
+
+<h3 id="back-doors">Mobile Back Doors</h3>
+<!-- INSERT back-doors.list -->
+
+<h3 id="insecurity">Mobile Insecurity</h3>
+
+<p>These bugs are/were not intentional, so unlike the rest of the file
+ they do not count as malware. We mention them to refute the
+ supposition that prestigious proprietary software doesn't have grave
+ bugs.</p>
+<!-- INSERT insecurity.list -->
+
+<h3 id="surveillance">Mobile Surveillance</h3>
+<!-- INSERT surveillance.list -->
+
+<h3 id="drm">Mobile DRM</h3>
+<!-- INSERT drm.list -->
+
+<h3 id="jails">Mobile Jails</h3>
+<!-- INSERT jails.list -->
+
+<h3 id="tyrants">Mobile Tyrants</h3>
+<!-- INSERT tyrants.list -->
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden";><address@hidden></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF. Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+ files generated as part of manuals) on the GNU web server should
+ be under CC BY-ND 4.0. Please do NOT change or remove this
+ without talking with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the
+ document. For web pages, it is ok to list just the latest year the
+ document was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright © 2014, 2015, 2016, 2017, 2018 Free Software Foundation,
Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by/4.0/";>Creative
+Commons Attribution 4.0 International License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/09/16 10:09:28 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
Index: mobile-stub.html
===================================================================
RCS file: mobile-stub.html
diff -N mobile-stub.html
--- mobile-stub.html 14 Sep 2018 21:12:47 -0000 1.1
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,193 +0,0 @@
-<!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.85 -->
-<title>Malware in Mobile Devices
-- GNU Project - Free Software Foundation</title>
-<style type="text/css" media="print,screen"><!--
-li dl { margin-top: .3em; }
-li dl dt { margin: .3em 0 0 0; font-weight: normal; font-style: italic; }
-li dl dd { margin: 0 3%; }
---></style>
-<!--#include virtual="/proprietary/po/malware-mobiles.translist" -->
-<!--#include virtual="/server/banner.html" -->
-<h2>Malware in Mobile Devices</h2>
-
-<p><a href="/proprietary/proprietary.html">Other examples of proprietary
-malware</a></p>
-
-<div class="highlight-para">
-<p>
-<em>Malware</em> means software designed to function in ways that
-mistreat or harm the user. (This does not include accidental errors.)
-</p>
-
-<p>
-Malware and nonfree software are two different issues. The difference
-between <a href="/philosophy/free-sw.html">free software</a> and
-nonfree software is in <a
-href="/philosophy/free-software-even-more-important.html">
-whether the users have control of the program or vice versa</a>. It's
-not directly a question of what the program <em>does</em> when it
-runs. However, in practice nonfree software is often malware, because
-the developer's awareness that the users would be powerless to fix any
-malicious functionalities tempts the developer to impose some.
-</p>
-
-<p>Nearly all mobile phones do two grievous wrongs to their users:
-tracking their movements, and listening to their conversations. This
-is why we call them “Stalin's dream”.</p>
-
-<p>If you know of an example that ought to be in this page but isn't
-here, please write
-to <a href="mailto:address@hidden";><address@hidden></a>
-to inform us. Please include the URL of a trustworthy reference or two
-to present the specifics.</p>
-</div>
-
-<ul>
- <li><p>The phone network
- <a href="https://ssd.eff.org/en/module/problem-mobile-phones";>
- tracks the movements of each phone</a>.</p>
- <p>This is inherent in the design of the phone network: as long as
- the phone is in communication with the network, there is no way
- to stop the network from recording its location. Many countries
- (including the US and the EU) require the network to store all
- these location data for months or years.</p>
- </li>
- <li><p id="universal-back-door">Almost every phone's communication processor
has
- a universal back door which
- is <a
href="https://www.schneier.com/blog/archives/2006/12/remotely_eavesd_1.html";>
- often used to make a phone transmit all conversations it
- hears</a>.</p>
- <p>The back
- door <a
href="http://www.osnews.com/story/27416/The_second_operating_system_hiding_in_every_mobile_phone";>
- may take the form of bugs that have gone 20 years unfixed</a>.
- The choice to leave the security holes in place is morally
- equivalent to writing a back door.</p>
- <p>The back door is in the “modem processor”, whose
- job is to communicate with the radio network. In most phones,
- the modem processor controls the microphone. In most phones it
- has the power to rewrite the software for the main processor
- too.</p>
- <p>A few phone models are specially designed so that the modem
- processor does not control the microphone, and so that it can't
- change the software in the main processor. They still have the
- back door, but at least it is unable to turn the phone unto a
- listening device.</p>
- <p>The universal back door is apparently also used to make phones
- <a
href="http://www.slate.com/blogs/future_tense/2013/07/22/nsa_can_reportedly_track_cellphones_even_when_they_re_turned_off.html";>
- transmit even when they are turned off</a>. This means their movements
- are tracked, and may also make the listening feature work.</p>
- </li>
-</ul>
-
-<p>Here are examples of malware in mobile devices. See also
-the <a href="/proprietary/malware-apple.html">the Apple malware
-page</a> for malicious functionalities specific to the Apple iThings.</p>
-
-<div class="summary" style="margin-top: 1em">
-<h3>Type of malware</h3>
-<ul>
-<li><a href="#back-doors">Back doors</a></li>
-<!--<li><a href="#censorship">Censorship</a></li>-->
-<li><a href="#insecurity">Insecurity</a></li>
-<!--<li><a href="#sabotage">Sabotage</a></li>-->
-<!--<li><a href="#interference">Interference</a></li>-->
-<li><a href="#surveillance">Surveillance</a></li>
-<li><a href="#drm">Digital restrictions
- management</a> or “DRM” means functionalities designed
- to restrict what users can do with the data in their computers.</li>
-<li><a href="#jails">Jails</a>—systems
- that impose censorship on application programs.</li>
-<li><a href="#tyrants">Tyrants</a>—systems
- that reject any operating system not “authorized” by the
- manufacturer.</li>
-</ul>
-</div>
-
-<h3 id="back-doors">Mobile Back Doors</h3>
-<!-- INSERT back-doors.list -->
-
-<h3 id="insecurity">Mobile Insecurity</h3>
-
-<p>These bugs are/were not intentional, so unlike the rest of the file
- they do not count as malware. We mention them to refute the
- supposition that prestigious proprietary software doesn't have grave
- bugs.</p>
-<!-- INSERT insecurity.list -->
-
-<h3 id="surveillance">Mobile Surveillance</h3>
-<!-- INSERT surveillance.list -->
-
-<h3 id="drm">Mobile DRM</h3>
-<!-- INSERT drm.list -->
-
-<h3 id="jails">Mobile Jails</h3>
-<!-- INSERT jails.list -->
-
-<h3 id="tyrants">Mobile Tyrants</h3>
-<!-- INSERT tyrants.list -->
-
-</div><!-- for id="content", starts in the include above -->
-<!--#include virtual="/server/footer.html" -->
-<div id="footer">
-<div class="unprintable">
-
-<p>Please send general FSF & GNU inquiries to
-<a href="mailto:address@hidden";><address@hidden></a>.
-There are also <a href="/contact/">other ways to contact</a>
-the FSF. Broken links and other corrections or suggestions can be sent
-to <a href="mailto:address@hidden";><address@hidden></a>.</p>
-
-<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
- replace it with the translation of these two:
-
- We work hard and do our best to provide accurate, good quality
- translations. However, we are not exempt from imperfection.
- Please send your comments and general suggestions in this regard
- to <a href="mailto:address@hidden";>
- <address@hidden></a>.</p>
-
- <p>For information on coordinating and submitting translations of
- our web pages, see <a
- href="/server/standards/README.translations.html">Translations
- README</a>. -->
-Please see the <a
-href="/server/standards/README.translations.html">Translations
-README</a> for information on coordinating and submitting translations
-of this article.</p>
-</div>
-
-<!-- Regarding copyright, in general, standalone pages (as opposed to
- files generated as part of manuals) on the GNU web server should
- be under CC BY-ND 4.0. Please do NOT change or remove this
- without talking with the webmasters or licensing team first.
- Please make sure the copyright date is consistent with the
- document. For web pages, it is ok to list just the latest year the
- document was modified, or published.
-
- If you wish to list earlier years, that is ok too.
- Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
- years, as long as each year in the range is in fact a copyrightable
- year, i.e., a year in which the document was published (including
- being publicly visible on the web or in a revision control system).
-
- There is more detail about copyright years in the GNU Maintainers
- Information document, www.gnu.org/prep/maintain. -->
-
-<p>Copyright © 2014, 2015, 2016, 2017, 2018 Free Software Foundation,
Inc.</p>
-
-<p>This page is licensed under a <a rel="license"
-href="http://creativecommons.org/licenses/by/4.0/";>Creative
-Commons Attribution 4.0 International License</a>.</p>
-
-<!--#include virtual="/server/bottom-notes.html" -->
-
-<p class="unprintable">Updated:
-<!-- timestamp start -->
-$Date: 2018/09/14 21:12:47 $
-<!-- timestamp end -->
-</p>
-</div>
-</div>
-</body>
-</html>
- www/server/staging/proprietary/rec mobiles-stub...,
Therese Godefroy <=