[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/proprietary malware-google.ru.html propriet...
From: |
GNUN |
Subject: |
www/proprietary malware-google.ru.html propriet... |
Date: |
Wed, 8 Mar 2017 10:59:27 -0500 (EST) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 17/03/08 10:59:27
Modified files:
proprietary : malware-google.ru.html
proprietary-censorship.fr.html
proprietary/po : malware-google.ru-en.html malware-google.ru.po
malware-google.translist
Added files:
proprietary : malware-google.fr.html
proprietary/po : malware-google.fr-en.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/malware-google.ru.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/proprietary-censorship.fr.html?cvsroot=www&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/malware-google.fr.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-google.ru-en.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-google.ru.po?cvsroot=www&r1=1.6&r2=1.7
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-google.translist?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/malware-google.fr-en.html?cvsroot=www&rev=1.1
Patches:
Index: malware-google.ru.html
===================================================================
RCS file: /web/www/www/proprietary/malware-google.ru.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- malware-google.ru.html 8 Mar 2017 09:30:17 -0000 1.1
+++ malware-google.ru.html 8 Mar 2017 15:59:27 -0000 1.2
@@ -39,16 +39,13 @@
<ul>
<li><a href="#back-doors"> Ðазейки</a></li>
<li><a href="#censorship"> ЦензÑÑа</a></li>
+ <li><a href="#insecurity"> УÑзвимоÑÑÑ</a></li>
-<!--<li>
-<a href="#insecurity">Insecurity</a></li>-->
-<!--<li>
+ <!--<li>
<a href="#pressuring">Pressuring</a></li>-->
<li><a href="#sabotage">СабоÑаж</a></li>
-
- <!--<li>
-<a href="#surveillance">Surveillance</a></li>-->
-<li><a href="#drm">ЦиÑÑовое ÑпÑавление
огÑаниÑениÑми</a>, или “DRM”
+ <li><a href="#surveillance">Слежка</a></li>
+ <li><a href="#drm">ЦиÑÑовое ÑпÑавление
огÑаниÑениÑми</a>, или “DRM”
ознаÑÐ°ÐµÑ ÑÑнкÑии, ÑпÑоекÑиÑованнÑе длÑ
огÑаниÑÐµÐ½Ð¸Ñ Ñого, ÑÑо полÑзоваÑели
могÑÑ Ð´ÐµÐ»Ð°ÑÑ Ñ Ð´Ð°Ð½Ð½Ñми на ÑвоиÑ
компÑÑÑеÑаÑ
.</li>
@@ -69,22 +66,6 @@
href="https://consumerist.com/2017/01/18/why-is-google-blocking-this-ad-blocker-on-chrome/">лазейка
Ð´Ð»Ñ Ñдаленного ÑÑиÑÐ°Ð½Ð¸Ñ Ð´Ð¾Ð¿Ð¾Ð»Ð½ÐµÐ½Ð¸Ð¹</a>.</p>
</li>
- <li>
- <p>РнеÑвободной библиоÑеке Baidu, Moplus, еÑÑÑ
лазейка, Ñ Ð¿Ð¾Ð¼Ð¾ÑÑÑ ÐºÐ¾ÑоÑой <a
-href="https://www.eff.org/deeplinks/2015/11/millions-android-devices-vulnerable-remote-hijacking-baidu-wrote-code-google-made">можно
-“вÑÑÑлаÑÑ ÑÐ°Ð¹Ð»Ñ Ð½Ð° ÑеÑвеє, а Ñакже
пÑинÑдиÑелÑно ÑÑÑанавливаÑÑ
-пÑиложениÑ</a>.</p>
- <p>Ðна пÑименÑеÑÑÑ Ð² 14000 пÑиложениÑÑ
Android.</p>
- </li>
-<li>
-<p><a
-href="http://www.theguardian.com/technology/2014/dec/18/chinese-android-phones-coolpad-hacker-backdoor">
-РкиÑайÑкой веÑÑии Android еÑÑÑ ÑнивеÑÑалÑнÑй
ÑеÑнÑй Ñ
од</a>. ÐоÑÑи во вÑеÑ
-моделÑÑ
мобилÑнÑÑ
ÑелеÑонов еÑÑÑ
ÑнивеÑÑалÑнÑй ÑеÑнÑй Ñ
од в модеме. ÐÐ»Ñ Ñего
-же компании Coolpad понадобилоÑÑ Ð²Ð²Ð¾Ð´Ð¸ÑÑ ÐµÑе
один? ÐоÑÐ¾Ð¼Ñ ÑÑо ÑÑÐ¾Ñ ÑеÑнÑй
-Ñ
од конÑÑолиÑÑеÑÑÑ ÐºÐ¾Ð¼Ð¿Ð°Ð½Ð¸ÐµÐ¹ Coolpad.
-</p>
-</li>
<li><p>Ð Android <a
href="http://www.computerworld.com/article/2506557/security0/google-throws--kill-switch--on-android-phones.html">
Ñ Google еÑÑÑ ÑеÑнÑй Ñ
од Ð´Ð»Ñ ÑдалениÑ
пÑогÑамм по ÑеÑи</a> (в пÑогÑамме под
@@ -104,12 +85,6 @@
<em>ÑдалениÑ</em> пÑогÑамм опÑавдаÑÑ Ð½ÐµÐ»ÑзÑ, и
Ñ Ð²Ð°Ñ Ð´Ð¾Ð»Ð¶Ð½Ð¾ бÑÑÑ Ð¿Ñаво
ÑеÑаÑÑ, ÐºÐ¾Ð¼Ñ Ð´Ð¾Ð²ÐµÑÑÑÑ Ñаким обÑазом (и
довеÑÑÑÑ Ð»Ð¸ комÑ-нибÑÐ´Ñ Ð²Ð¾Ð¾Ð±Ñе).</p></li>
- <li><p><a id="samsung"
-href="https://www.fsf.org/blogs/community/replicant-developers-find-and-close-samsung-galaxy-backdoor">
-УÑÑÑойÑÑва Samsung Galaxy под ÑпÑавлением
неÑвободнÑÑ
веÑÑий Android
-поÑÑавлÑÑÑÑÑ Ñ Ð»Ð°Ð·ÐµÐ¹ÐºÐ¾Ð¹</a>, коÑоÑаÑ
пÑедоÑÑавлÑÐµÑ ÑдаленнÑй доÑÑÑп к
-Ñайлам, Ñ
ÑанÑÑимÑÑ Ð½Ð° ÑÑÑÑойÑÑве.</p></li>
-
</ul>
<h3 id="censorship">ЦензÑÑа</h3>
<ul>
@@ -133,13 +108,26 @@
ÑпоÑобами. СвободнÑе пÑогÑÐ°Ð¼Ð¼Ñ Ð¼Ð¾Ð¶Ð½Ð¾
ÑÑÑанавливаÑÑ Ð¸Ð· f-droid.org.</p></li>
</ul>
+<h3 id="insecurity">УÑзвимоÑÑÑ</h3>
+<ul>
+ <li><p><a
+href="http://www.spiegel.de/international/world/privacy-scandal-nsa-can-spy-on-smart-phone-data-a-920971.html">
+ÐÐÐ Ð¼Ð¾Ð¶ÐµÑ Ð·Ð°Ð³Ð»ÑдÑваÑÑ Ð² даннÑе на
ÑмаÑÑÑонаÑ
, в Ñом ÑиÑле на iPhone, Android
+и BlackBerry</a>. ХоÑÑ Ð¿Ð¾Ð´ÑобноÑÑи здеÑÑ Ð½Ðµ
пÑиводÑÑÑÑ, поÑ
оже, ÑÑо ÑабоÑаеÑ
+не как ÑнивеÑÑалÑнÑй ÑеÑнÑй Ñ
од, коÑоÑÑй,
как Ð¼Ñ Ð·Ð½Ð°ÐµÐ¼, еÑÑÑ Ð¿Ð¾ÑÑи во вÑеÑ
+мобилÑнÑÑ
ÑелеÑонаÑ
. ÐÑо Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ
ÑвÑзано Ñ ÑкÑплÑаÑаÑией ÑазлиÑнÑÑ
+оÑибок. <a
+href="http://www.osnews.com/story/27416/The_second_operating_system_hiding_in_every_mobile_phone">
+РпÑогÑаммаÑ
ÑадиоаппаÑаÑÑÑÑ ÑелеÑонов
еÑÑÑ Ð¼Ð½Ð¾Ð¶ÐµÑÑво оÑибок</a>.</p></li>
+</ul>
+
<h3 id="sabotage">СабоÑаж</h3>
<p>ÐеÑпÑаведливоÑÑи из ÑÑого Ñаздела,
ÑÑÑого говоÑÑ, не вÑедоноÑнÑе пÑогÑаммÑ,
поÑколÑÐºÑ Ð¾Ð½Ð¸ не подÑазÑмеваÑÑ
изгоÑовление пÑогÑаммÑ, коÑоÑÐ°Ñ ÑабоÑаеÑ
Ñак,
ÑÑо ÑÑо вÑÐµÐ´Ð¸Ñ Ð¿Ð¾Ð»ÑзоваÑелÑ. Ðо ÑÑо оÑенÑ
ÑÑ
одно Ñ Ð²ÑедоноÑнÑми пÑогÑаммами,
-поÑколÑÐºÑ ÑÑо ÑеÑ
ниÑеÑкие дейÑÑÐ²Ð¸Ñ Apple,
коÑоÑÑе вÑедÑÑ Ð¿Ð¾Ð»ÑзоваÑелÑм
-конкÑеÑнÑÑ
пÑогÑамм Apple.</p>
+поÑколÑÐºÑ ÑÑо ÑеÑ
ниÑеÑкие дейÑÑÐ²Ð¸Ñ Google,
коÑоÑÑе вÑедÑÑ Ð¿Ð¾Ð»ÑзоваÑелÑм
+конкÑеÑнÑÑ
пÑогÑамм Google.</p>
<ul>
<li><p>У Google долго бÑла <a
@@ -147,34 +135,10 @@
лазейка Ð´Ð»Ñ Ñдаленного оÑпиÑаниÑ
ÑÑÑÑойÑÑва на базе Android</a>, еÑли ÑолÑко
его диÑк не заÑиÑÑован (ÑÑо возможно
наÑÐ¸Ð½Ð°Ñ Ñ Android 5.0 Lollipop, но
оÑнÑÐ´Ñ Ð½Ðµ по ÑмолÑаниÑ.)</p></li>
+</ul>
- <li><p>Ðолее 73% ÑамÑÑ
попÑлÑÑнÑÑ
пÑиложений
Android <a
-href="http://jots.pub/a/2015103001/index.php"> пÑедоÑÑавлÑÑÑ
лиÑнÑÑ,
-поведенÑеÑкÑÑ Ð¸ меÑÑоопÑеделиÑелÑнÑÑ
инÑоÑмаÑиÑ</a> ÑвоиÑ
полÑзоваÑелей
-ÑÑеÑÑим ÑÑоÑонам.
- </p></li>
-
- <li><p>“СкÑÑÑнÑе ÑообÑениє, не
ÑвÑзаннÑе Ñ ÑÑнкÑионалÑноÑÑÑÑ
-пÑиложениÑ, <a
-href="http://news.mit.edu/2015/data-transferred-android-apps-hiding-1119">
-Ð½Ð°Ð¹Ð´ÐµÐ½Ñ Ð² 500 ÑамÑÑ
попÑлÑÑнÑÑ
беÑплаÑнÑÑ
пÑиложениÑÑ
Android</a>.</p>
-
- <p>Ð ÑÑаÑÑе не Ñледовало опиÑÑваÑÑ ÑÑи
пÑÐ¸Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ ÐºÐ°Ðº “<span lang="en"
-xml:lang="en">free</span>) (ÑвободнÑе)”, они не
ÑвободнÑ. ЯÑное Ñлово
-Ð´Ð»Ñ Ð²ÑÑÐ°Ð¶ÐµÐ½Ð¸Ñ Ð½Ñлевой ÑÐµÐ½Ñ —
“беÑплаÑнÑй”.</p>
-
- <p>Ð ÑÑаÑÑе пÑинимаеÑÑÑ ÐºÐ°Ðº Ñамо Ñобой
ÑазÑмеÑÑееÑÑ, ÑÑо обÑÑнÑй аналиÑиÑеÑкий
-инÑÑÑÑменÑаÑий пÑавомеÑен, но веÑно ли
ÑÑо? У ÑазÑабоÑÑиков пÑогÑамм неÑ
-пÑава анализиÑоваÑÑ, ÑÑо и как делаÑÑ
-полÑзоваÑели. “ÐналиÑиÑеÑкие”
инÑÑÑÑменÑÑ, коÑоÑÑе подглÑдÑваÑÑ,
-ниÑем не лÑÑÑе лÑбого дÑÑгого
подглÑдÑваниÑ.</p></li>
-
- <li><p>ÐеÑплаÑнÑе (но не <a
-href="/philosophy/free-sw.html">ÑвободнÑе</a>)пÑиложениÑ
Android <a
-href="http://www.theguardian.com/technology/2015/may/06/free-android-apps-connect-tracking-advertising-websites">подклÑÑаÑÑÑÑ
-к 100 URL Ñлежки и ÑекламÑ</a> (в ÑÑеднем).</p>
- </li>
-
+<h3 id="surveillance">Слежка</h3>
+<ul>
<li><p>ÐÑогÑаммÑ-ÑÐ¿Ð¸Ð¾Ð½Ñ Ð¿ÑиÑÑÑÑÑвÑÑÑ Ð½Ð°
некоÑоÑÑÑ
ÑÑÑÑойÑÑваÑ
Android, когда они
пÑодаÑÑÑÑ. РнекоÑоÑÑÑ
ÑелеÑонаÑ
Motorola
ÑиÑÑема Android изменена Ð´Ð»Ñ <a
href="http://www.beneaththewaves.net/Projects/Motorola_Is_Listening.html">
@@ -230,16 +194,6 @@
пÑедÑÑмаÑÑÐ¸Ð²Ð°ÐµÑ ÑÑнкÑии, пÑедназнаÑеннÑе
Ð´Ð»Ñ Ð¿Ð¾Ð´Ð´ÐµÑжки ÑиÑÑового ÑпÑавлениÑ
огÑаниÑениÑми</a>.</p>
</li>
-
- <li><p><a
-href="http://www.spiegel.de/international/world/privacy-scandal-nsa-can-spy-on-smart-phone-data-a-920971.html">
-ÐÐÐ Ð¼Ð¾Ð¶ÐµÑ Ð·Ð°Ð³Ð»ÑдÑваÑÑ Ð² даннÑе на
ÑмаÑÑÑонаÑ
, в Ñом ÑиÑле на iPhone, Android
-и BlackBerry</a>. ХоÑÑ Ð¿Ð¾Ð´ÑобноÑÑи здеÑÑ Ð½Ðµ
пÑиводÑÑÑÑ, поÑ
оже, ÑÑо ÑабоÑаеÑ
-не как ÑнивеÑÑалÑнÑй ÑеÑнÑй Ñ
од, коÑоÑÑй,
как Ð¼Ñ Ð·Ð½Ð°ÐµÐ¼, еÑÑÑ Ð¿Ð¾ÑÑи во вÑеÑ
-мобилÑнÑÑ
ÑелеÑонаÑ
. ÐÑо Ð¼Ð¾Ð¶ÐµÑ Ð±ÑÑÑ
ÑвÑзано Ñ ÑкÑплÑаÑаÑией ÑазлиÑнÑÑ
-оÑибок. <a
-href="http://www.osnews.com/story/27416/The_second_operating_system_hiding_in_every_mobile_phone">
-РпÑогÑаммаÑ
ÑадиоаппаÑаÑÑÑÑ ÑелеÑонов
еÑÑÑ Ð¼Ð½Ð¾Ð¶ÐµÑÑво оÑибок</a>.</p></li>
</ul>
<h3 id="tyrants">ТиÑанÑ</h3>
@@ -331,7 +285,7 @@
<p class="unprintable"><!-- timestamp start -->
Ðбновлено:
-$Date: 2017/03/08 09:30:17 $
+$Date: 2017/03/08 15:59:27 $
<!-- timestamp end -->
</p>
Index: proprietary-censorship.fr.html
===================================================================
RCS file: /web/www/www/proprietary/proprietary-censorship.fr.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- proprietary-censorship.fr.html 1 Feb 2017 12:01:16 -0000 1.15
+++ proprietary-censorship.fr.html 8 Mar 2017 15:59:27 -0000 1.16
@@ -97,13 +97,14 @@
(et s'en servent pour surveiller les utilisateurs).</p>
<p>Le bloqueur de pubs est un logiciel propriétaire, tout comme le programme
-(Google Play) que Google utilisait pour en refuser l'accès en vue d'une
-installation. Utiliser un programme non libre donne à son propriétaire du
+(Google Play) dont Google se servait pour vous empêcher de
+l'installer. Utiliser un programme non libre donne à son propriétaire du
pouvoir sur vous ; c'est ce pouvoir qu'a exercé Google </p>
<p>La censure de Google, contrairement à celle d'Apple ou Microsoft, n'est pas
complète. Android permet aux utiliateurs d'installer des applis
-autrement. Vous pouvez installer des programmes libres sur f-droid.org.</p>
+autrement. Vous pouvez installer des programmes libres provenant de
+f-droid.org.</p>
</li>
<li><p>
@@ -192,7 +193,7 @@
<p class="unprintable"><!-- timestamp start -->
Dernière mise à jour :
-$Date: 2017/02/01 12:01:16 $
+$Date: 2017/03/08 15:59:27 $
<!-- timestamp end -->
</p>
Index: po/malware-google.ru-en.html
===================================================================
RCS file: /web/www/www/proprietary/po/malware-google.ru-en.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/malware-google.ru-en.html 8 Mar 2017 09:30:17 -0000 1.1
+++ po/malware-google.ru-en.html 8 Mar 2017 15:59:27 -0000 1.2
@@ -34,10 +34,10 @@
<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="#insecurity">Insecurity</a></li>
<!--<li><a href="#pressuring">Pressuring</a></li>-->
<li><a href="#sabotage">Sabotage</a></li>
- <!--<li><a href="#surveillance">Surveillance</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>
@@ -55,21 +55,6 @@
<li><p>Chrome has a back door <a
href="https://consumerist.com/2017/01/18/why-is-google-blocking-this-ad-blocker-on-chrome/">for
remote erasure of add-ons</a>.</p>
</li>
- <li>
- <p>Baidu's proprietary Android library, Moplus, has a back door
- that <a
href="https://www.eff.org/deeplinks/2015/11/millions-android-devices-vulnerable-remote-hijacking-baidu-wrote-code-google-made">can
- “upload files” as well as forcibly install
- apps</a>.</p>
- <p>It is used by 14,000 Android applications.</p>
- </li>
-<li>
-<p><a
href="http://www.theguardian.com/technology/2014/dec/18/chinese-android-phones-coolpad-hacker-backdoor">
-A Chinese version of Android has a universal back door</a>. Nearly all
-models of mobile phones have a universal back door in the modem chip. So
-why did Coolpad bother to introduce another? Because this one is controlled
-by Coolpad.
-</p>
-</li>
<li><p>In Android, <a
href="http://www.computerworld.com/article/2506557/security0/google-throws--kill-switch--on-android-phones.html">
Google has a back door to remotely delete apps.</a> (It is in a program
called GTalkService).</p>
@@ -89,10 +74,6 @@
to <em>delete</em> the programs, and you should have the right to
decide who (if anyone) to trust in this way.</p></li>
- <li><p><a id="samsung"
href="https://www.fsf.org/blogs/community/replicant-developers-find-and-close-samsung-galaxy-backdoor">
- Samsung Galaxy devices running proprietary Android versions come with a
back
- door</a> that provides remote access to the files stored on the
device.</p></li>
-
</ul>
<h3 id="censorship">Google Censorship</h3>
<ul>
@@ -113,12 +94,23 @@
free programs from f-droid.org.</p></li>
</ul>
+<h3 id="insecurity">Google Insecurity</h3>
+<ul>
+ <li><p><a
href="http://www.spiegel.de/international/world/privacy-scandal-nsa-can-spy-on-smart-phone-data-a-920971.html">
+ The NSA can tap data in smart phones, including iPhones, Android, and
+ BlackBerry</a>. While there is not much detail here, it seems that
+ this does not operate via the universal back door that we know nearly
+ all portable phones have. It may involve exploiting various bugs.
+ There are <a
href="http://www.osnews.com/story/27416/The_second_operating_system_hiding_in_every_mobile_phone">
+ lots of bugs in the phones' radio software</a>.</p></li>
+</ul>
+
<h3 id="sabotage">Google Sabotage</h3>
<p>The wrongs in this section are not precisely malware, since they do
not involve making the program that runs in a way that hurts the user.
-But they are a lot like malware, since they are technical Apple
-actions that harm to the users of specific Apple software.</p>
+But they are a lot like malware, since they are technical Google
+actions that harm to the users of specific Google software.</p>
<ul>
<li><p>Google has long had <a
@@ -126,30 +118,10 @@
back door to remotely unlock an Android device</a>, unless its
disk is encrypted (possible since Android 5.0 Lollipop, but
still not quite the default).</p></li>
+</ul>
- <li><p>More than 73% of the most popular Android apps <a
href="http://jots.pub/a/2015103001/index.php">share personal,
- behavioral and location information</a> of their users with third
parties.
- </p></li>
-
- <li><p>“Cryptic communication,” unrelated to the app's
functionality,
- was <a
href="http://news.mit.edu/2015/data-transferred-android-apps-hiding-1119">
- found in the 500 most popular gratis Android apps</a>.</p>
-
- <p>The article should not have described these apps as
- “free”—they are not free software. The clear way to
say
- “zero price” is “gratis.”</p>
-
- <p>The article takes for granted that the usual analytics tools are
- legitimate, but is that valid? Software developers have no right to
- analyze what users are doing or how. “Analytics” tools that
snoop are
- just as wrong as any other snooping.</p></li>
-
- <li><p>Gratis Android apps (but not <a href="/philosophy/free-sw.html">free
software</a>)
- connect to 100
- <a
href="http://www.theguardian.com/technology/2015/may/06/free-android-apps-connect-tracking-advertising-websites">tracking
and advertising</a> URLs,
- on the average.</p>
- </li>
-
+<h3 id="surveillance">Google Surveillance</h3>
+<ul>
<li><p>Spyware is present in some Android devices when they are sold.
Some Motorola phones modify Android to
<a
href="http://www.beneaththewaves.net/Projects/Motorola_Is_Listening.html">
@@ -199,14 +171,6 @@
<li><p>Android <a
href="https://developer.android.com/reference/android/drm/package-summary.html">contains
facilities specifically to support DRM.</a></p>
</li>
-
- <li><p><a
href="http://www.spiegel.de/international/world/privacy-scandal-nsa-can-spy-on-smart-phone-data-a-920971.html">
- The NSA can tap data in smart phones, including iPhones, Android, and
- BlackBerry</a>. While there is not much detail here, it seems that
- this does not operate via the universal back door that we know nearly
- all portable phones have. It may involve exploiting various bugs.
- There are <a
href="http://www.osnews.com/story/27416/The_second_operating_system_hiding_in_every_mobile_phone">
- lots of bugs in the phones' radio software</a>.</p></li>
</ul>
<h3 id="tyrants">Google Tyrants</h3>
@@ -276,7 +240,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/03/08 09:30:17 $
+$Date: 2017/03/08 15:59:27 $
<!-- timestamp end -->
</p>
</div>
Index: po/malware-google.ru.po
===================================================================
RCS file: /web/www/www/proprietary/po/malware-google.ru.po,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- po/malware-google.ru.po 8 Mar 2017 15:38:23 -0000 1.6
+++ po/malware-google.ru.po 8 Mar 2017 15:59:27 -0000 1.7
@@ -15,7 +15,6 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"X-Outdated-Since: 2017-03-08 10:26+0000\n"
#. type: Content of: <title>
msgid "Google's Software Is Malware - GNU Project - Free Software Foundation"
@@ -80,9 +79,6 @@
msgstr "<a href=\"#censorship\"> ЦензÑÑа</a>"
#. type: Content of: <div><ul><li>
-# | <a [-href=\"#censorship\">Censorship</a>-]
-# | {+href=\"#insecurity\">Insecurity</a>+}
-#| msgid "<a href=\"#censorship\">Censorship</a>"
msgid "<a href=\"#insecurity\">Insecurity</a>"
msgstr "<a href=\"#insecurity\"> УÑзвимоÑÑÑ</a>"
@@ -91,9 +87,6 @@
msgstr "<a href=\"#sabotage\">СабоÑаж</a>"
#. type: Content of: <div><ul><li>
-# | <a [-href=\"#sabotage\">Sabotage</a>-]
-# | {+href=\"#surveillance\">Surveillance</a>+}
-#| msgid "<a href=\"#sabotage\">Sabotage</a>"
msgid "<a href=\"#surveillance\">Surveillance</a>"
msgstr "<a href=\"#surveillance\">Слежка</a>"
@@ -219,8 +212,6 @@
"СвободнÑе пÑогÑÐ°Ð¼Ð¼Ñ Ð¼Ð¾Ð¶Ð½Ð¾ ÑÑÑанавливаÑÑ
из f-droid.org."
#. type: Content of: <h3>
-# | Google [-Censorship-] {+Insecurity+}
-#| msgid "Google Censorship"
msgid "Google Insecurity"
msgstr "УÑзвимоÑÑÑ"
@@ -250,15 +241,6 @@
msgstr "СабоÑаж"
#. type: Content of: <p>
-# | The wrongs in this section are not precisely malware, since they do not
-# | involve making the program that runs in a way that hurts the user. But
-# | they are a lot like malware, since they are technical [-Apple-] {+Google+}
-# | actions that harm to the users of specific [-Apple-] {+Google+} software.
-#| msgid ""
-#| "The wrongs in this section are not precisely malware, since they do not "
-#| "involve making the program that runs in a way that hurts the user. But "
-#| "they are a lot like malware, since they are technical Apple actions that "
-#| "harm to the users of specific Apple software."
msgid ""
"The wrongs in this section are not precisely malware, since they do not "
"involve making the program that runs in a way that hurts the user. But they "
@@ -286,8 +268,6 @@
"оÑнÑÐ´Ñ Ð½Ðµ по ÑмолÑаниÑ.)"
#. type: Content of: <h3>
-# | Google [-Tyrants-] {+Surveillance+}
-#| msgid "Google Tyrants"
msgid "Google Surveillance"
msgstr "Слежка"
Index: po/malware-google.translist
===================================================================
RCS file: /web/www/www/proprietary/po/malware-google.translist,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- po/malware-google.translist 8 Mar 2017 09:30:17 -0000 1.2
+++ po/malware-google.translist 8 Mar 2017 15:59:27 -0000 1.3
@@ -3,10 +3,12 @@
value='<div id="translations">
<p>
<span dir="ltr" class="original"><a lang="en" hreflang="en"
href="/proprietary/malware-google.en.html">English</a> [en]</span>
+<span dir="ltr"><a lang="fr" hreflang="fr"
href="/proprietary/malware-google.fr.html">français</a> [fr]</span>
<span dir="ltr"><a lang="ru" hreflang="ru"
href="/proprietary/malware-google.ru.html">ÑÑÑÑкий</a> [ru]</span>
</p>
</div>' -->
<link rel="alternate" type="text/html" href="/proprietary/malware-google.html"
hreflang="x-default" />
<link rel="alternate" type="text/html" lang="en" hreflang="en"
href="/proprietary/malware-google.en.html" title="English" />
+<link rel="alternate" type="text/html" lang="fr" hreflang="fr"
href="/proprietary/malware-google.fr.html" title="français" />
<link rel="alternate" type="text/html" lang="ru" hreflang="ru"
href="/proprietary/malware-google.ru.html" title="ÑÑÑÑкий" />
<!-- end translist file -->
Index: malware-google.fr.html
===================================================================
RCS file: malware-google.fr.html
diff -N malware-google.fr.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ malware-google.fr.html 8 Mar 2017 15:59:26 -0000 1.1
@@ -0,0 +1,300 @@
+<!--#set var="ENGLISH_PAGE" value="/proprietary/malware-google.en.html" -->
+
+<!--#include virtual="/server/header.fr.html" -->
+<!-- Parent-Version: 1.83 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Malveillance des logiciels de Google - Projet GNU - Free Software
Foundation</title>
+
+<!--#include virtual="/proprietary/po/malware-google.translist" -->
+<!--#include virtual="/server/banner.fr.html" -->
+<h2>Malveillance des logiciels de Google</h2>
+
+<p><a href="/proprietary/proprietary.html">Autres exemples de malveillance dans
+le logiciel privateur</a></p>
+
+<div class="highlight-para">
+<p>
+Un logiciel est dit « malveillant » lorsque son fonctionnement a été
conçu
+pour traiter l'utilisateur de manière inéquitable ou lui faire du tort
+(erreurs accidentelles mises à part). Cette page explique ce qui rend
+malveillants les logiciels de Google.
+</p>
+
+<p>Logiciel malveillant et logiciel non libre sont deux notions différentes.
La
+différence entre <a href="/philosophy/free-sw.html">logiciel libre</a> et
+logiciel non libre réside dans le fait que <a
+href="/philosophy/free-software-even-more-important.html">les utilisateurs
+ont, ou non, le contrôle du programme</a>. Cela n'a rien à voir avec ce que
+<em>fait</em> le programme en cours de fonctionnement. Cependant, en
+pratique, un logiciel non libre est souvent malveillant parce que le
+développeur, conscient que les utilisateurs seraient incapables de corriger
+une éventuelle fonctionnalité malveillante, est tenté de leur en imposer
+quelques-unes.
+</p>
+</div>
+
+<div class="summary" style="margin-top: 2em">
+ <h3><strong>Type de malveillance</strong></h3>
+ <ul>
+ <li><a href="#back-doors">Portes dérobées</a></li>
+ <li><a href="#censorship">Censure</a></li>
+ <li><a href="#insecurity">Insécurité</a></li>
+
+ <!--<li>
+<a href="#pressuring">Pressuring</a></li>-->
+<li><a href="#sabotage">Sabotage</a></li>
+ <li><a href="#surveillance">Surveillance</a></li>
+ <li><a href="#drm">Gestion numérique des restrictions</a>, ou <abbr
+title="Digital Restrictions Management">DRM</abbr> â fonctionnalités
conçues
+pour restreindre ce que les utilisateurs peuvent faire avec les données
+présentes sur leur ordinateur.</li>
+
+ <!--<li>
+<a href="#jails">Jails</a>—systems
+ that impose censorship on application programs.</li>-->
+<li><a href="#tyrants">Tyrans</a> â systèmes qui rejettent tout système
+d'exploitation non « autorisé » par le fabricant.</li>
+
+ <!--<li>
+<a href="#deception">Deception</a></li>-->
+</ul>
+</div>
+
+<h3 id="back-doors">Portes dérobées</h3>
+<ul>
+ <li><p>Chrome a une porte dérobée <a
+href="https://consumerist.com/2017/01/18/why-is-google-blocking-this-ad-blocker-on-chrome/">pour
+l'effacement à distance des modules complémentaires</a>.</p>
+ </li>
+ <li><p>Dans Android, <a
+href="http://www.computerworld.com/article/2506557/security0/google-throws--kill-switch--on-android-phones.html">Google
+a une porte dérobée qui lui permet de supprimer des applications Ã
+distance</a> (elle est dans un programme appelé GTalkService).</p>
+
+ <p>Via GTalkService, Google peut aussi <a
+href="https://jon.oberheide.org/blog/2010/06/25/remote-kill-and-install-on-google-android/">installer
+des applis, de force et à distance</a> (ce service semble avoir fusionné
+avec Google Play depuis la parution de cet article). Ce n'est pas
+l'équivalent d'une porte dérobée universelle, mais cela rend possibles
+divers mauvais coups.</p>
+
+ <p>Bien que <em>l'exercice</em> de ce pouvoir par Google n'ait pas été
+malfaisant jusqu'à présent, le fait est que personne ne doit posséder un tel
+pouvoir, car il pourrait aussi être utilisé de manière malfaisante. Vous
+pourriez parfaitement décider de laisser un service de sécurité
+<em>désactiver</em> à distance les programmes qu'il considère comme
+malveillants. Mais il n'y a aucune excuse pour les <em>supprimer</em>, et
+vous devez avoir le droit de décider à qui accorder une telle confiance (Ã
+supposer que vous l'accordiez à quelqu'un).</p></li>
+
+</ul>
+<h3 id="censorship">Censure</h3>
+<ul>
+
+ <li><p>Google <a
+href="https://consumerist.com/2017/01/18/why-is-google-blocking-this-ad-blocker-on-chrome/">censure
+les modules complémentaires de Chrome</a>.</p></li>
+ <li><p><a
+href="http://www.theguardian.com/media/2016/feb/03/google-pulls-ad-blocking-app-for-samsung-phones">Google
+a censuré l'installation du bloqueur de pubs de Samsung</a> en disant que
+bloquer les pubs revenait à « interférer » avec les sites qui en
affichent
+(et s'en servent pour surveiller les utilisateurs).</p>
+
+ <p>Le bloqueur de pubs est un logiciel propriétaire, tout comme le
programme
+(Google Play) dont Google se servait pour vous empêcher de
+l'installer. Utiliser un programme non libre donne à son propriétaire du
+pouvoir sur vous ; c'est ce pouvoir qu'a exercé Google </p>
+
+ <p>La censure de Google, contrairement à celle d'Apple ou Microsoft,
n'est pas
+complète. Android permet aux utiliateurs d'installer des applis
+autrement. Vous pouvez installer des programmes libres provenant de
+f-droid.org.</p></li>
+</ul>
+
+<h3 id="insecurity">Insécurité</h3>
+<ul>
+ <li><p><a
+href="http://www.spiegel.de/international/world/privacy-scandal-nsa-can-spy-on-smart-phone-data-a-920971.html">La
+NSA peut aller chercher des données dans les smartphones, que ce soit les
+iPhones, les Android ou les Blackberry</a>. Bien que l'article soit peu
+détaillé, il semble que cette opération n'utilise pas la porte dérobée
+universelle qui, on le sait, se trouve dans presque tous les téléphones
+portables. Il est possible qu'elle exploite différentes bogues. Il y a de
+plus <a
+href="http://www.osnews.com/story/27416/The_second_operating_system_hiding_in_every_mobile_phone">une
+multitude de bogues dans le logiciel de radio des téléphones</a>.</p></li>
+</ul>
+
+<h3 id="sabotage">Sabotage</h3>
+
+<p>Les injustices décrites dans cette section ne sont pas précisément de la
+malveillance car elles ne sous-entendent pas que le programme en
+fonctionnement soit conçu pour nuire à l'utilisateur. Mais elles y
+ressemblent beaucoup puisqu'il s'agit d'actions techniques de Google qui
+font du tort aux utilisateurs de certains programmes de Google.</p>
+
+<ul>
+ <li><p>Google a depuis longtemps <a
+href="http://www.theguardian.com/technology/2015/nov/24/google-can-unlock-android-devices-remotely-if-phone-unencrypted">une
+porte dérobée qui sert à déverrouiller les appareils Android Ã
distance</a>,
+à moins que leur disque ne soit chiffré (le chiffrement est possible depuis
+Android Lollipop, mais n'est pas encore activé par défaut).</p></li>
+</ul>
+
+<h3 id="surveillance">Surveillance</h3>
+<ul>
+ <li><p>Des logiciels espions sont présents dans certains appareils sous
Android au
+moment de l'achat. Dans certains téléphones Motorola, Android a été
modifié
+<a
+href="http://www.beneaththewaves.net/Projects/Motorola_Is_Listening.html">de
+manière à communiquer des données personnelles au fabricant</a>.</p>
+ </li>
+
+ <li><p>Des logiciels espions dans les téléphones Android et les ordinateurs
+portables (sous Windows ?) : le <cite>Wall Street Journal</cite> (dans un
+article pourvu d'une barrière à péage) rapporte que <a
+href="http://www.theverge.com/2013/8/1/4580718/fbi-can-remotely-activate-android-and-laptop-microphones-reports-wsj">le
+FBI peut activer à distance le GPS et le micro des téléphones Android et des
+ordinateurs portables</a> (je soupçonne qu'ils parlent des ordinateurs sous
+Windows)Â ; voici des <a
+href="http://cryptome.org/2013/08/fbi-hackers.htm">informations
+complémentaires</a>.</p>
+ </li>
+
+ <li><p>La nouvelle appli de messagerie vocale de Google <a
+href="http://www.theverge.com/2016/9/21/12994362/allo-privacy-message-logs-google">enregistre
+toutes les conversations</a>.</p>
+ </li>
+ <li><p>Les thermomètres de Nest envoient au serveur <a
+href="http://bgr.com/2014/07/17/google-nest-jailbreak-hack">beaucoup de
+données concernant l'utilisateur</a>.</p>
+ </li>
+
+ <li><p>De nombreux sites envoient à Google un rapport sur chacun de leurs
visiteurs
+par le biais de Google Analytics, rapport qui contient <a
+href="http://www.pcworld.idg.com.au/article/434164/google_analytics_breaks_norwegian_privacy_laws_local_agency_said/">son
+adresse IP et la page visitée</a>. </p>
+ </li>
+
+ <li><p>Dans Google Chrome, les extensions ont toute facilité pour <a
+href="https://labs.detectify.com/2015/07/28/how-i-disabled-your-chrome-security-extensions/">espionner
+en détail la navigation de l'utilisateur</a>, et beaucoup ne s'en privent
+pas.</p>
+ </li>
+</ul>
+
+<h3 id="drm">DRM</h3>
+<ul>
+<li>
+ <p>Chrome <a
+href="http://boingboing.net/2017/01/30/google-quietly-makes-optiona.html">met
+en Åuvre la gestion numérique des restrictions</a>, de même que Chromium, Ã
+l'aide d'un logiciel non libre intégré.</p>
+
+ <p><a
href="https://bugs.chromium.org/p/chromium/issues/detail?id=686430">Pour
+en savoir plus</a>.</p>
+</li>
+
+<li><p>Android <a
+href="https://developer.android.com/reference/android/drm/package-summary.html">a
+des fonctionnalités spéciales pour gérer les DRM.</a></p>
+</li>
+</ul>
+
+<h3 id="tyrants">Tyrans</h3>
+<ul>
+ <li>
+<p><a
+href="http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html">Certains
+téléphones portables Android sont des tyrans</a> (bien que quelqu'un ait
+trouvé moyen de briser ces restrictions). Fort heureusement, la plupart des
+appareils Android ne sont pas des tyrans.
+</p>
+</li>
+</ul>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.fr.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Veuillez envoyer les requêtes concernant la FSF et GNU à <a
+href="mailto:address@hidden"><address@hidden></a>. Il existe aussi <a
+href="/contact/">d'autres moyens de contacter</a> la FSF. Les liens
+orphelins et autres corrections ou suggestions peuvent être signalés à <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>. -->
+Nous faisons le maximum pour proposer des traductions fidèles et de bonne
+qualité, mais nous ne sommes pas parfaits. Merci d'adresser vos commentaires
+sur cette page, ainsi que vos suggestions d'ordre général sur les
+traductions, Ã <a href="mailto:address@hidden">
+<address@hidden></a>.</p>
+<p>Pour tout renseignement sur la coordination et la soumission des
+traductions de nos pages web, reportez-vous au <a
+href="/server/standards/README.translations.html">guide de traduction</a>.</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 © 2017 Free Software Foundation, Inc.</p>
+
+<p>Cette page peut être utilisée suivant les conditions de la licence <a
+rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/deed.fr">Creative
+Commons attribution, pas de modification, 4.0Â internationale (CCÂ BY-ND
+4.0)</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.fr.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+Traduction et révision : <a
+href="mailto:trad-gnu@april.org">trad-gnu@april.org</a></div>
+
+<p class="unprintable"><!-- timestamp start -->
+Dernière mise à jour :
+
+$Date: 2017/03/08 15:59:26 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
Index: po/malware-google.fr-en.html
===================================================================
RCS file: po/malware-google.fr-en.html
diff -N po/malware-google.fr-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/malware-google.fr-en.html 8 Mar 2017 15:59:27 -0000 1.1
@@ -0,0 +1,249 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.83 -->
+<title>Google's Software Is Malware
+- GNU Project - Free Software Foundation</title>
+ <!--#include virtual="/proprietary/po/malware-google.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<h2>Google's Software is Malware</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.)
+This page explains how Google software is malware.
+</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>
+</div>
+
+<div class="summary" style="margin-top: 2em">
+ <h3><strong>Type of malware</strong></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="#pressuring">Pressuring</a></li>-->
+ <li><a href="#sabotage">Sabotage</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>
+ <!--<li><a href="#deception">Deception</a></li>-->
+ </ul>
+</div>
+
+<h3 id="back-doors">Google Back Doors</h3>
+<ul>
+ <li><p>Chrome has a back door <a
href="https://consumerist.com/2017/01/18/why-is-google-blocking-this-ad-blocker-on-chrome/">for
+ remote erasure of add-ons</a>.</p>
+ </li>
+ <li><p>In Android, <a
href="http://www.computerworld.com/article/2506557/security0/google-throws--kill-switch--on-android-phones.html">
+ Google has a back door to remotely delete apps.</a> (It is in a program
+ called GTalkService).</p>
+
+ <p>Google can also
+ <a
href="https://jon.oberheide.org/blog/2010/06/25/remote-kill-and-install-on-google-android/">
+ forcibly and remotely install apps</a> through GTalkService (which
+ seems, since that article, to have been merged into Google Play).
+ This is not equivalent to a universal back door, but permits various
+ dirty tricks.</p>
+
+ <p>Although Google's <em>exercise</em> of this power has not been
+ malicious so far, the point is that nobody should have such power,
+ which could also be used maliciously. You might well decide to let a
+ security service remotely <em>deactivate</em> programs that it
+ considers malicious. But there is no excuse for allowing it
+ to <em>delete</em> the programs, and you should have the right to
+ decide who (if anyone) to trust in this way.</p></li>
+
+</ul>
+<h3 id="censorship">Google Censorship</h3>
+<ul>
+
+ <li><p>Google <a
href="https://consumerist.com/2017/01/18/why-is-google-blocking-this-ad-blocker-on-chrome/">censors
+ add-ons for Chrome</a>.</p></li>
+ <li><p><a
href="http://www.theguardian.com/media/2016/feb/03/google-pulls-ad-blocking-app-for-samsung-phones">Google
+ censored installation of Samsung's ad-blocker,</a> saying that
+ blocking ads is “interference” with the sites that
+ advertise (and surveil users through ads).</p>
+
+ <p>The ad-blocker is proprietary software, just like the program (Google
+ Play) that Google used to deny access to install it. Using a nonfree
program
+ gives the owner power over you, and Google has exercised that power.</p>
+
+ <p>Google's censorship, unlike that of Apple and Microsoft, is not total:
+ Android allows users to install apps in other ways. You can install
+ free programs from f-droid.org.</p></li>
+</ul>
+
+<h3 id="insecurity">Google Insecurity</h3>
+<ul>
+ <li><p><a
href="http://www.spiegel.de/international/world/privacy-scandal-nsa-can-spy-on-smart-phone-data-a-920971.html">
+ The NSA can tap data in smart phones, including iPhones, Android, and
+ BlackBerry</a>. While there is not much detail here, it seems that
+ this does not operate via the universal back door that we know nearly
+ all portable phones have. It may involve exploiting various bugs.
+ There are <a
href="http://www.osnews.com/story/27416/The_second_operating_system_hiding_in_every_mobile_phone">
+ lots of bugs in the phones' radio software</a>.</p></li>
+</ul>
+
+<h3 id="sabotage">Google Sabotage</h3>
+
+<p>The wrongs in this section are not precisely malware, since they do
+not involve making the program that runs in a way that hurts the user.
+But they are a lot like malware, since they are technical Google
+actions that harm to the users of specific Google software.</p>
+
+<ul>
+ <li><p>Google has long had <a
+
href="http://www.theguardian.com/technology/2015/nov/24/google-can-unlock-android-devices-remotely-if-phone-unencrypted">a
+ back door to remotely unlock an Android device</a>, unless its
+ disk is encrypted (possible since Android 5.0 Lollipop, but
+ still not quite the default).</p></li>
+</ul>
+
+<h3 id="surveillance">Google Surveillance</h3>
+<ul>
+ <li><p>Spyware is present in some Android devices when they are sold.
+ Some Motorola phones modify Android to
+ <a
href="http://www.beneaththewaves.net/Projects/Motorola_Is_Listening.html">
+ send personal data to Motorola</a>.</p>
+ </li>
+
+ <li><p>Spyware in Android phones (and Windows? laptops): The Wall
+ Street Journal (in an article blocked from us by a paywall)
+ reports that
+ <a
href="http://www.theverge.com/2013/8/1/4580718/fbi-can-remotely-activate-android-and-laptop-microphones-reports-wsj">
+ the FBI can remotely activate the GPS and microphone in Android
+ phones and laptops</a>.
+ (I suspect this means Windows laptops.) Here is
+ <a href="http://cryptome.org/2013/08/fbi-hackers.htm">more info</a>.</p>
+ </li>
+
+ <li><p>Google's new voice messaging app <a
href="http://www.theverge.com/2016/9/21/12994362/allo-privacy-message-logs-google">logs
+ all conversations</a>.</p>
+ </li>
+ <li><p>Nest thermometers
+ send <a href="http://bgr.com/2014/07/17/google-nest-jailbreak-hack">a
+ lot of data about the user</a>.</p>
+ </li>
+
+ <li><p>Many web sites report all their visitors to Google by using
+ the Google Analytics service, which
+ <a
href="http://www.pcworld.idg.com.au/article/434164/google_analytics_breaks_norwegian_privacy_laws_local_agency_said/">
+ tells Google the IP address and the page that was visited.</a></p>
+ </li>
+
+ <li><p>Google Chrome makes it easy for an extension to do <a
+
href="https://labs.detectify.com/2015/07/28/how-i-disabled-your-chrome-security-extensions/">total
+ snooping on the user's browsing</a>, and many of them do so.</p>
+ </li>
+</ul>
+
+<h3 id="drm">Google DRM</h3>
+<ul>
+<li>
+ <p>Chrome <a
href="http://boingboing.net/2017/01/30/google-quietly-makes-optiona.html">implements
+ DRM</a>. So does Chromium, through nonfree software that is
+ effectively part of it.</p>
+
+ <p><a
href="https://bugs.chromium.org/p/chromium/issues/detail?id=686430">More
information</a>.</p>
+</li>
+
+<li><p>Android <a
href="https://developer.android.com/reference/android/drm/package-summary.html">contains
+facilities specifically to support DRM.</a></p>
+</li>
+</ul>
+
+<h3 id="tyrants">Google Tyrants</h3>
+<ul>
+ <li>
+<p><a
href="http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html">
+Some Android phones are tyrants</a> (though someone found a way to
+crack the restriction). Fortunately, most Android devices are not tyrants.
+</p>
+</li>
+</ul>
+
+</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 © 2017 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2017/03/08 15:59:27 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/proprietary malware-google.ru.html propriet...,
GNUN <=