www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/philosophy/proprietary po/malware-mobiles.e...


From: GNUN
Subject: www/philosophy/proprietary po/malware-mobiles.e...
Date: Wed, 19 Nov 2014 13:00:30 +0000

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     14/11/19 13:00:30

Modified files:
        philosophy/proprietary/po: malware-mobiles.es.po 
                                   malware-mobiles.translist 
Added files:
        philosophy/proprietary: malware-mobiles.es.html 
        philosophy/proprietary/po: malware-mobiles.es-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/proprietary/malware-mobiles.es.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/proprietary/po/malware-mobiles.es.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/proprietary/po/malware-mobiles.translist?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/proprietary/po/malware-mobiles.es-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/malware-mobiles.es.po
===================================================================
RCS file: /web/www/www/philosophy/proprietary/po/malware-mobiles.es.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/malware-mobiles.es.po    19 Nov 2014 12:38:21 -0000      1.1
+++ po/malware-mobiles.es.po    19 Nov 2014 13:00:29 -0000      1.2
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: malware-mobiles.html\n"
-"POT-Creation-Date: 2014-11-19 13:40+0100\n"
+"POT-Creation-Date: 2014-11-18 10:33+0000\n"
 "PO-Revision-Date: 2014-11-19 13:23+0100\n"
 "Last-Translator: Dora Scilipoti <dora AT gnu DOT org>\n"
 "Language-Team: Spanish <address@hidden>\n"
@@ -313,11 +313,6 @@
 msgid "Copyright &copy; 2014 Free Software Foundation, Inc."
 msgstr "Copyright &copy; 2014 Free Software Foundation, Inc."
 
-#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
-#. type: Content of: <div><div>
-msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*"
-msgstr "<strong>Traducción: Moisés Muñoz, 2014.</strong>"
-
 #. type: Content of: <div><p>
 msgid ""
 "This page is licensed under a <a rel=\"license\" href=\"http://";
@@ -328,6 +323,11 @@
 "org/licenses/by-nd/3.0/us/deed.es\">licencia Creative Commons Atribución-"
 "SinDerivadas 3.0 Estados Unidos de América</a>."
 
+#. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.
+#. type: Content of: <div><div>
+msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*"
+msgstr "<strong>Traducción: Moisés Muñoz, 2014.</strong>"
+
 # type: Content of: <div><p>
 #.  timestamp start 
 #. type: Content of: <div><p>

Index: po/malware-mobiles.translist
===================================================================
RCS file: /web/www/www/philosophy/proprietary/po/malware-mobiles.translist,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- po/malware-mobiles.translist        30 Aug 2014 10:27:18 -0000      1.2
+++ po/malware-mobiles.translist        19 Nov 2014 13:00:30 -0000      1.3
@@ -4,6 +4,7 @@
 <p>
 <span dir="ltr" class="original"><a lang="en" hreflang="en" 
href="/philosophy/proprietary/malware-mobiles.en.html">English</a>&nbsp;[en]</span>
 &nbsp;
 <span dir="ltr"><a lang="de" hreflang="de" 
href="/philosophy/proprietary/malware-mobiles.de.html">Deutsch</a>&nbsp;[de]</span>
 &nbsp;
+<span dir="ltr"><a lang="es" hreflang="es" 
href="/philosophy/proprietary/malware-mobiles.es.html">español</a>&nbsp;[es]</span>
 &nbsp;
 <span dir="ltr"><a lang="fr" hreflang="fr" 
href="/philosophy/proprietary/malware-mobiles.fr.html">français</a>&nbsp;[fr]</span>
 &nbsp;
 <span dir="ltr"><a lang="ru" hreflang="ru" 
href="/philosophy/proprietary/malware-mobiles.ru.html">русский</a>&nbsp;[ru]</span>
 &nbsp;
 </p>

Index: malware-mobiles.es.html
===================================================================
RCS file: malware-mobiles.es.html
diff -N malware-mobiles.es.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ malware-mobiles.es.html     19 Nov 2014 13:00:25 -0000      1.1
@@ -0,0 +1,227 @@
+<!--#set var="ENGLISH_PAGE" 
value="/philosophy/proprietary/malware-mobiles.en.html" -->
+
+<!--#include virtual="/server/header.es.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Malware en los dispositivos móviles - Proyecto GNU - Free Software
+Foundation</title>
+
+<!--#include virtual="/philosophy/proprietary/po/malware-mobiles.translist" -->
+<!--#include virtual="/server/banner.es.html" -->
+<h2><cite>Malware</cite> en los dispositivos móviles</h2>
+
+<a href="/philosophy/proprietary/proprietary.html">Más ejemplos de
+<cite>malware</cite> en el software privativo</a>
+
+<p>
+<cite>Malware</cite> se refiere al software que es dañino, es decir, que
+está diseñado de tal forma que su funcionamiento maltrata o daña al usuario
+(no se tienen aquí­ en cuenta los errores involuntarios).
+</p>
+
+<p>
+El <cite>malware</cite> y el software que no es libre son dos cosas
+diferentes. La diferencia entre el <a
+href="/philosophy/free-sw.html">software libre</a> y el software que no es
+libre reside en <a
+href="/philosophy/free-software-even-more-important.html"> si los usuarios
+controlan el programa o por el contrario el programa controla a los
+usuarios</a>. No es una cuestión directamente relacionada con lo que el
+programa <em>hace</em> cuando se ejecuta. De todas maneras, en la práctica,
+el software que no es libre a menudo es también <cite>malware</cite>. Esto
+se debe a que el desarrollador, sabiendo que a los usuarios se les ha negado
+la posibilidad de poner remedio a las funcionalidades maliciosas, se ve
+tentado a imponer algunas.
+</p>
+
+<p>Estos son ejemplos de la presencia de <em>malware</em> en los dispositivos
+móviles. Véase también la <a
+href="/philosophy/proprietary/malware-apple.html"> página de programas
+dañinos de Apple</a>, donde se mencionan las funcionalidades maliciosas
+específicas de las iCosas de Apple.</p>
+
+<ul>
+  <li><p>Los teléfonos móviles con GPS envían la ubicación GPS mediante 
comando
+remoto y los usuarios no pueden detenerlos: <a
+href="http://www.aclu.org/government-location-tracking-cell-phones-gps-devices-and-license-plate-readers";>
+http://www.aclu.org/government-location-tracking-cell-phones-gps-devices-and-license-plate-readers</a>.
+(EE. UU. dice que eventualmente exigirá que todos los teléfonos móviles
+nuevos tengan GPS).</p>
+  </li>
+
+  <li><p>La mayoría de los teléfonos móviles tienen una puerta trasera 
universal que
+ha sido utilizada para <a
+href="http://www.slate.com/blogs/future_tense/2013/07/22/nsa_can_reportedly_track_cellphones_even_when_they_re_turned_off.html";>
+convertirlos en maliciosos</a>.</p>
+  </li>
+
+  <li><p><a
+href="https://www.fsf.org/blogs/community/replicant-developers-find-and-close-samsung-galaxy-backdoor";>
+Los dispositivos Samsung Galaxy que ejecutan versiones privativas de Android
+cuentan con una puerta trasera</a> que permite el acceso remoto a los datos
+almacenados en el dispositivo.</p>
+  </li>
+
+  <li><p><a
+href="http://www.spiegel.de/international/world/privacy-scandal-nsa-can-spy-on-smart-phone-data-a-920971.html";>
+La NSA puede pinchar datos en los teléfonos inteligentes, incluyendo los
+iPhone, Android y BlackBerry</a>. Si bien el artículo no ofrece mayores
+detalles, al parecer estos dispositivos no utilizan la puerta trasera
+universal que, como sabemos, casi todos los teléfonos móviles tienen. Puede
+que su funcionamiento implique la explotación de diversos fallos. <a
+href="http://www.osnews.com/story/27416/The_second_operating_system_hiding_in_every_mobile_phone";>El
+software de radio de los teléfonos contiene muchos fallos</a>.</p>
+  </li>
+
+  <li><p>Software espía en los teléfonos Cisco VoIP TNP: <a
+href="http://boingboing.net/2012/12/29/your-cisco-phone-is-listening.html";>
+http://boingboing.net/2012/12/29/your-cisco-phone-is-listening.html</a>.</p></li>
+
+  <li><p>Software espía en los teléfonos Android y ordenadores portátiles 
(¿con
+Windows?): El periódico <cite>The Wall Street Journal</cite>, en un artículo
+que no podemos leer a causa de una barrera de pago, informa que <a
+href="http://www.theverge.com/2013/8/1/4580718/fbi-can-remotely-activate-android-and-laptop-microphones-reports-wsj";>
+el FBI puede activar remotamente el GPS y el micrófono en los teléfonos
+Android y ordenadores portátiles</a> (sospecho que se refieren a los
+portátiles con Windows). Aquí hay <a
+href="http://cryptome.org/2013/08/fbi-hackers.htm";>más información</a>.</p>
+  </li>
+
+  <li><p>Algunos teléfonos Motorola modifican Android para <a
+href="http://www.beneaththewaves.net/Projects/Motorola_Is_Listening.html";>
+enviar datos personales a Motorola.</a></p>
+  </li>
+
+  <li><p>Algunos fabricantes añaden un <a
+href="http://androidsecuritytest.com/features/logs-and-services/loggers/carrieriq/";>
+paquete de vigilancia general oculto tales como Carrier IQ.</a></p>
+  </li>
+
+  <li><p><a 
href="/philosophy/proprietary/proprietary-back-doors.html#samsung"> La
+puerta trasera de Samsung</a> permite el acceso a cualquier archivo del
+sistema.</p>
+  </li>
+
+  <li>
+  <p>En Android, <a
+href="http://www.computerworld.com/article/2506557/security0/google-throws--kill-switch--on-android-phones.html";>Google
+tiene una puerta trasera para eliminar aplicaciones remotamente</a> (está en
+un programa llamado GTalkService).
+  </p>
+
+  <p>
+  Google también puede <a
+href="https://jon.oberheide.org/blog/2010/06/25/remote-kill-and-install-on-google-android/";>instalar
+aplicaciones por la fuerza y remotamente</a> a través de GTalkService (que
+al parecer se fusionó con Google Play después que se escribió ese
+artículo). Se trata en fin de cuentas de una puerta trasera universal.
+  </p>
+ 
+  <p>
+  Si bien hasta el momento Google no ha <em>ejercido</em> este poder de manera
+maliciosa, el hecho es que nadie debe tener tal poder, pues también podría
+utilizarse con malicia. Uno bien podría tomar la decisión de dejar que un
+servicio de seguridad <em>desactive</em> remotamente programas que considere
+maliciosos, pero no hay excusas para autorizar la <em>eliminación</em> de
+los programas. Debemos tener el derecho de decidir en quién confiar, o de no
+confiar en nadie.
+  </p>
+  </li>
+
+  <li><p><a
+href="http://blog.azimuthsecurity.com/2013/04/unlocking-motorola-bootloader.html";>
+Algunos teléfonos Android son tiranos</a> (aunque alguien encontró una
+manera de saltarse la restricción). Afortunadamente, la mayoría de los
+dispositivos Android no son tiranos.</p>
+  </li>
+
+  <li><p><a href="http://fsf.org/campaigns/secure-boot-vs-restricted-boot/";> 
Los
+dispositivos móviles con Windows 8 son tiranos</a>. <a
+href="http://www.itworld.com/operating-systems/301057/microsoft-metro-app-store-lockdown";>
+Windows 8 en los «dispositivos móviles» es una prisión.</a></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.es.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Envíe sus consultas acerca de la FSF y GNU a <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>. Existen también <a
+href="/contact/">otros medios para contactar</a> con la FSF. <br /> Para
+avisar de enlaces rotos y proponer otras correcciones o sugerencias,
+diríjase a <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</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";>
+
+        &lt;address@hidden&gt;</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>. -->
+El equipo de traductores al español se esfuerza por ofrecer traducciones
+fieles al original y de buena calidad, pero no estamos libres de cometer
+errores.<br /> Por favor envíe sus comentarios y sugerencias sobre las
+traducciones a <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+</p><p>Consulte la <a href="/server/standards/README.translations.html">Guía
+para las traducciones</a> para obtener información sobre la coordinación y
+el envío de traducciones de las páginas de este sitio web.</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 3.0 US.  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 &copy; 2014 Free Software Foundation, Inc.</p>
+
+<p>Esta página está bajo una <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.es";>licencia
+Creative Commons Atribución-SinDerivadas 3.0 Estados Unidos de 
América</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.es.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Traducción: Moisés Muñoz, 2014.</strong></div>
+
+<p class="unprintable"><!-- timestamp start -->
+Última actualización:
+
+$Date: 2014/11/19 13:00:25 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/malware-mobiles.es-en.html
===================================================================
RCS file: po/malware-mobiles.es-en.html
diff -N po/malware-mobiles.es-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/malware-mobiles.es-en.html       19 Nov 2014 13:00:29 -0000      1.1
@@ -0,0 +1,190 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>Malware in Mobile Devices
+- GNU Project - Free Software Foundation</title>
+ <!--#include virtual="/philosophy/proprietary/po/malware-mobiles.translist" 
-->
+<!--#include virtual="/server/banner.html" -->
+<h2>Malware in Mobile Devices</h2>
+
+<a href="/philosophy/proprietary.html">Other examples of proprietary 
+malware</a>
+
+<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>Here are examples of malware in mobile devices.  See also
+the <a href="/philosophy/malware-apple.html">the Apple malware
+page</a> for malicious functionalities specific to the Apple iThings.</p>
+
+<ul>
+  <li><p>Portable phones with GPS will send their GPS location on remote
+  command and users cannot stop them: <a 
+  
href="http://www.aclu.org/government-location-tracking-cell-phones-gps-devices-and-license-plate-readers";>
+  
http://www.aclu.org/government-location-tracking-cell-phones-gps-devices-and-license-plate-readers</a>.
 
+  (The US says it will eventually require all new portable phones to have 
+  GPS.)</p>
+  </li>
+
+  <li><p>Most mobile phones have a universal back door, which has been 
+  used to <a 
+  
href="http://www.slate.com/blogs/future_tense/2013/07/22/nsa_can_reportedly_track_cellphones_even_when_they_re_turned_off.html";>
+  turn them malicious</a>.</p>
+  </li>
+
+  <li><p><a 
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 data stored on the 
+  device.</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>
+
+  <li><p>Spyware in Cisco TNP IP phones: <a 
+  href="http://boingboing.net/2012/12/29/your-cisco-phone-is-listening.html";>
+  
http://boingboing.net/2012/12/29/your-cisco-phone-is-listening.html</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>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>Some manufacturers add a <a 
+  
href="http://androidsecuritytest.com/features/logs-and-services/loggers/carrieriq/";>
+  hidden general surveillance package such as Carrier IQ.</a></p>
+  </li>
+
+  <li><p><a href="/philosophy/proprietary/proprietary-back-doors.html#samsung">
+  Samsung's back door</a> provides access to any file on the system.</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 adds up to
+  a universal back door.
+  </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>
+
+  <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>
+
+  <li><p><a href="http://fsf.org/campaigns/secure-boot-vs-restricted-boot/";>
+  Mobile devices that come with Windows 8 are tyrants</a>. <a 
+  
href="http://www.itworld.com/operating-systems/301057/microsoft-metro-app-store-lockdown";>
+  Windows 8 on &ldquo;mobile devices&rdquo; is a jail.</a></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 &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</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";>&lt;address@hidden&gt;</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";>
+        &lt;address@hidden&gt;</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 3.0 US.  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 &copy; 2014 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2014/11/19 13:00:29 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]