es/index.html

   1 <!DOCTYPE html>
   2 <html>
   3         <head>
   4                         <meta charset="utf-8">
   5
   6                         <title>Email Self-Defense - una guía para la lucha contra la vigilancia con el cifrado GnuPG</title>
   7                         <meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy, email, Enigmail" />
   8       <meta name="description" content="La vigilancia al correo electrónico viola nuestros derechos fundamentales y pone en riesgo la libertad de expresión. Esta guía te enseñara *auto-defensa de e-mail en 30 minutos* con GnuPG.">
   9
  10       <meta name="viewport" content="width=device-width, initial-scale=1">
  11                         <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css">
  12                 <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />
  13
  14         </head>
  15         <body>
  16
  17 <!-- ~~~~~~~~~ GnuPG Header and introduction text  ~~~~~~~~~ -->
  18
  19                 <header class="row"  id="header">
  20                         <div>
  21                           <h1>Email Self-Defense</h1>
  22
  23                           <!-- Language list for browsers that do not have JS enabled -->
  24                           <ul id="languages" class="os">
  25                             <li><a href="/en">english</a></li>
  26                             <li><a class="current" href="/es">español</a></li>
  27                             <li><a href="/fr">français</a></li>
  28                             <li><a href="/de">deutsch</a></li>
  29                             <li><a href="/pt-br">português do Brasil</a></li>
  30                             <li><a href="/tr">türkçe</a></li>
  31                             <li><a href="/ro">română</a></li>
  32                             <li><a href="/ru">русский</a></li>
  33                             <li><a href="/ml">മലയാളം</a></li>
  34                             <li><a href="/ko">한국어</a></li>
  35                             <li><a href="/ja">日本語</a></li>
  36                             <li><a href="/el">ελληνικά</a></li>
  37                           </ul>
  38
  39                           <ul id="menu" class="os">
  40                             <li class="spacer">
  41                               <a href="index.html" class="current">GNU/Linux</a>
  42                             </li>
  43                             <li>
  44                               <a href="mac.html">Mac OS</a>
  45                             </li>
  46                             <li>
  47                               <a href="windows.html">Windows</a>
  48                             </li>
  49                             <li class="spacer">
  50                               <a href="https://fsf.org/share?u=https://u.fsf.org/zb&amp;t=Email encryption for everyone via %40fsf">
  51                                 #EmailSelfDefense
  52                               </a>
  53                             </li>
  54                           </ul>
  55
  56                                 <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
  57                                 <div id="fsf-intro">
  58                                   <h3>
  59                                     <a href="http://u.fsf.org/ys">
  60                                       <img alt="Free Software Foundation"
  61                                            src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png">
  62                                     </a>
  63                                   </h3>
  64                                   <div class="fsf-emphasis">
  65                                     <p>
  66                                       Luchamos por los derechos de los usuarios de computadora, y promovemos el desarrollo del software libre. Resistir la vigilancia en masa es muy importante para nosotros
  67                                     </p>
  68                                     <p>
  69                                       <strong>
  70                                         Queremos promover fuertemente herramientas como esta, personalmente y en línea, para ayudar a tantas personas como sea posible a dar el primer paso hacia el uso de software libre para proteger su privacidad. ¿Puede hacer una donación o hacerse socio para ayudarnos a lograr esta meta?
  71                                       </strong>
  72                                     </p>
  73                                   </div>
  74
  75                                         <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=esd&pk_kwd=guide_donate"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/donate.en.png"></a>      <a href="https://u.fsf.org/yr"><img alt="Join now" src="//static.fsf.org/nosvn/enc-dev0/img/join.en.png"></a></p>
  76
  77                                 </div><!-- End #fsf-intro -->
  78
  79                                 <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
  80                                 <div class="intro">
  81                                         <p>
  82                                                 <a id="infographic" href="infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/infographic-button.png" alt="View &amp; share our infographic &rarr;" /></a>
  83                       La vigilancia en masa viola los derechos fundamentales y pone en riesgo la libertad de expresión. Esta guía te eseñara la habilidad básica de auto-defensa contra la vigilancia: cifrado de correo electrónico. Una vez la hayas finalizado, seras capaz de enviar y recibir correos electrónicos que estan codificados para asegurarse de que un agente de vigilancia o un ladrón que intercepte tu correo electrónico no pueda leerlo. Todo lo que necesitas es una computadora con conexión a Internet, una cuenta de correo electrónico, y aproximadamente media hora.
  84                     </p>
  85                     <p>
  86                       Incluso si no tienes nada que esconder, usar cifrado ayuda a proteger la privacidad de personas con las que te comunicas, y hace la vida díficil a los sistemas de vigilancia en masa. Si tienes algo importante que esconder, entonces estas en buena compañia; estas son las mismas herramientas que Edward Snowden uso para compartir sus famosos secretos sobre la NSA.
  87                     </p>
  88                     <p>
  89                       Adicionalmente a usar cifrado, hacer frente a la vigilancia necesita lucha política para <a href="http://gnu.org/philosophy/surveillance-vs-democracy.html">la reducción de la cantidad de datos recolectados sobre nosotros</a>, pero esencialmente el primer paso es protegerse a uno mismo y hacer que la vigilancia de tus comunicaciones lo más díficil posible. ¡Empecemos!
  90                     </p>
  91
  92                                 </div>
  93
  94                         </div>
  95                 </header><!-- End #header -->
  96
  97 <!-- ~~~~~~~~~ Section 1: Get the pieces  ~~~~~~~~~ -->
  98                 <section class="row" id="section1">
  99                         <div>
 100                                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 101                                 <div class="section-intro">
 102                                         <h2><em>#1</em> Consigue las piezas</h2>
 103                     <p class="notes">
 104                       Esta guía usa software que esta licenciado libremente; es completamente transparente y que cualquier persona puede copiar, o hacer su propia versión. Esto hace que sea más seguro contra la vigilancia que el software propietario (como Windows). Aprende más sobre software libre en <a href="https://u.fsf.org/ys">fsf.org</a>.
 105                     </p>
 106                     <p>
 107                       La mayoría de Sistemas Operativos GNU/Linux vienen con GnuPG ya instalado, por lo que no es necesario que lo descargues. De todas maneras antes de configurar GnuPG necesitarás un programa de correo electrónico de escritorio instalado en tu computadora. La mayoría de las distribuciones GNU/Linux tienen una versión libre del programa Thunderbird disponible para instalar. This guide will work with them, in addition to Thunderbird itself. Los programas de correo electrónico son otra manera de acceder a las mismas cuentas de correo electrónico a las que accedes usando un navegador (como Gmail), pero proporcionan características adicionales.
 108                     </p>
 109                     <p>
 110                       Si ya tienes alguno de estos, puedes saltar al <a href="#step-1b">Paso 1.b</a>.
 111                     </p>
 112                                 </div><!-- End .section-intro -->
 113
 114                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 115                                 <div id="step-1a" class="step">
 116                                         <div class="sidebar">
 117                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1a-install-wizard.png" alt="Step 1.A: Install Wizard" /></p>
 118                                         </div><!-- /.sidebar -->
 119                                         <div class="main">
 120                                                 <h3><em>Paso 1.a</em> Configura tu programa de correo electrónico con tu cuenta de correo(si todavia no esta)</h3>
 121                                                 <p>Abre tu programa de correo electrónico y sigue al asistente para configurar el programa con tu cuenta de correo electrónico.</p>
 122
 123                                                 <!-- ~~~~~~~~~ Solución de problemas  ~~~~~~~~~ -->
 124                                                 <div class="troubleshooting">
 125                                                         <h4>Solución de problemas</h4>
 126                                                         <dl>
 127                                                                 <dt>¿Qué es un asistente?</dt>
 128                                                                         <dd>Un asistente es una secuencia de ventanas que se abren para realizar algo de manera sencilla dentro de una computadora, como por ejemplo instalar un programa. Tu haces click a través, seleccionado opciones a medida que avanzas.</dd>
 129                                                                 <dt>Mi programa de correo electrónico no puede encontrar mi cuenta, o no esta descargando mi correo</dt>
 130                                                                         <dd>Antes de buscar en la Web, nosotros recomendamos que preguntes a otras personas que usan el mismo sistema de correo electrónico, para averguar las configuraciones correctas.</dd>
 131                                                                 <dt class="feedback">¿No encuentras una solución a tu problema?</dt>
 132                                                                         <dd class="feedback">Por favor háznoslo saber en la <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">página de comentarios</a>.</dd>
 133                                                         </dl>
 134                                                 </div><!-- /.troubleshooting -->
 135
 136                                         </div><!-- End .main -->
 137                                 </div><!-- End #step1-a .step -->
 138
 139                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 140                                 <div id="step-1b" class="step">
 141                                         <div class="sidebar">
 142                                                 <ul class="images">
 143                                                         <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-01-tools-addons.png" alt="Step 1.B: Tools -> Add-ons" /></li>
 144                                                         <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-02-search.png" alt="Step 1.B: Search Add-ons" /></li>
 145                                                         <li><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step1b-03-install.png" alt="Step 1.B: Install Add-ons" /></li>
 146                                                 </ul>
 147                                         </div><!-- /.sidebar -->
 148                                         <div class="main">
 149                                                 <h3><em>Paso 1.b</em> Instala el plugin Enigmail para tu programa de correo electrónico</h3>
 150                                                 <p>En el menú de tu programa de correo electrónico, selecciona Complementos(es posible que este en la sección de Herramientas). Asegurate de que Extensiones este seleccionada en la izquierda. ¿Puedes ver Enigmail? si es asi, entonces salta este paso.</p>
 151                                                 <p>Caso contrario, busca "Enigmail" usando la barra de busqueda en la esquina superior derecha. You can take it from here. Reinicia tu programa de correo electrónico cuando termines.</p>
 152                                                 <!-- ~~~~~~~~~ Solución de problemas  ~~~~~~~~~ -->
 153                                                 <div class="troubleshooting">
 154                                                         <h4>Solución de problemas</h4>
 155                                                         <dl>
 156                                                                 <dt>No puede encontrar el menú.</dt>
 157                                                                         <dd>En muchos programas de correo electrónico nuevos, el menú principal esta representado por una imágen de tres barras horizontales apiladas.</dd>
 158
 159                                                                 <dt class="feedback">¿No encuentras una solución a tu problema?</dt>
 160                                                                         <dd class="feedback">Por favor háznoslo saber en la <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">página de comentarios</a>.</dd>
 161                                                         </dl>
 162                                                 </div><!-- /.troubleshooting -->
 163                                         </div><!-- End .main -->
 164                                 </div><!-- End #step-1b .step -->
 165                         </div>
 166                 </section><!-- End #section1 -->
 167
 168 <!-- ~~~~~~~~~ Section 2: Make your keys  ~~~~~~~~~ -->
 169                 <section class="row" id="section2">
 170                         <div>
 171                                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 172                                 <div class="section-intro">
 173                                         <h2><em>#2</em> Haz tus llaves</h2>
 174                                         <p>Para usar el sistema GnuPG, necesitarás una llave pública y una llave privada (juntas conocidas como keypair). Cada una es una cadena larga de números y letras generada aleatoreamente que son únicos para ti. Tu llave pública y privada estan enlazadas entre si mediante una función matemática especial.</p>
 175                     <p>Tu llave pública no es similar a una llave física, debido a que es almacenada en un directorio en linea llamado keyserver. Las personas la descargan y la usan junto con GnuPG, para cifrar los correos electrónicos que te envian. Puedes pensar en el keyserver como en una guía telefónica, donde las personas que quieren enviarte un correo electrónico cifrado buscan tu llave pública.</p>
 176                     <p>Tu llave privada es más similar a una llave física, debido a que tu la guardas solo para ti (en tu computadora). Usas GnuPG y tu llave privada para descifrar correos electrónicos cifrados que otras personas te mandan.</p>
 177                                 </div><!-- End .section-intro -->
 178
 179                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 180                                 <div id="step-2a" class="step">
 181                                         <div class="sidebar">
 182                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/step2a-01-make-keypair.png" alt="Step 2.A: Make a Keypair" /></p>
 183                                         </div><!-- /.sidebar -->
 184                                         <div class="main">
 185                                                 <h3><em>Step 2.a</em> Crear un par de llaves</h3>
 186                                                 <p>En el menú de tu programa de e-mail, selecciona OpenPGP -> Asistente de configuración. No necesitas leer el texto en la ventana que emerge, a menos que lo quieras, pero es bueno leer el texto en las ultimas pantallas del asistente.</p>
 187                                                 <p>En la segunda pantalla titulada "Signing", selecciona "No, quiero crear reglas por destinatario para los e-mails que necesitan ser firmados."</p>
 188                                                 <p>Usar las opciones por defecto hasta llegar a la pantalla titulada "Crear llave."</p>
 189                                                 <p>En la pantalla titulada "Crear llave", elegir una contraseña segura! Tu contraseña debería ser de al menos 12 caracteres, e incluir al menos una letra minúscula y una mayúscula, y al menos un numero o símbolo de puntuación. No olvides la contraseña, o todo este trabajo sera en vano!.</p>
 190                                         <p class="notes">El programa tomara un pequeño tiempo mientras termina el siguiente paso, la pantalla de "Creación de llave". Mientras esperas, puedes hacer otras cosas con tu computadora, como mirar una película o navegar por la red. Cuanto mas utilices el equipo en este momento, mas rápida será la creación de la llave.</p>
 191                         <p>Cuando aparezca la pantalla de confirmación de OpenPGP , selecciona "Generar Certificado" y guárdalo en un lugar seguro en tu computadora (recomendamos crear una carpeta llamada "Certificado de Revocación" en tu carpeta home y guardarla ahí).</p>
 192                                                 <p>Aprenderás mas acerca de la revocación de certificado en la <a href="#section5">Sección 5</a>. El asistente te pedirá moverlo a un dispositivo externo, pero no es necesario en este momento.</p>
 193
 194                                                 <!-- ~~~~~~~~~ Solución de problemas  ~~~~~~~~~ -->
 195                                                 <div class="troubleshooting">
 196                                                         <h4>Solución de problemas</h4>
 197                                                         <dl>
 198                                                                 <dt>No puedo encontrar el menú OpenPGP.</dt>
 199                                                                     <dd>En muchos programas de correo electrónico nuevos, el menú principal esta representado por una por una imágen de tres barras horizontales apiladas. Es probable que OpenPGP este dentro de la sección Herramientas.</dd>
 200                                 <dt>El asistente de configuración dice que no pueden encontrar GnuPG.</dt>
 201                                     <dd>Abre el programa que generalmente usas para instalar software, y busca GnuPG, luego instalalo. A continuación reinicia el asistente de configuración de Engimail llendo a OpenPGP &rarr; Setup Wizard.</dd>
 202                                 <dt class="feedback">¿No encuentras una solución a tu problema?</dt>
 203                                                                         <dd class="feedback">Por favor háznoslo saber en la <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">página de comentarios</a>.</dd>
 204                                                         </dl>
 205                                                 </div><!-- /.troubleshooting -->
 206                                         </div><!-- End .main -->
 207                                 </div><!-- End #step-2a .step  -->
 208
 209                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 210                                 <div id="step-2b" class="step">
 211                                         <div class="main">
 212                                                 <h3><em>Step 2.b</em> Upload your public key to a keyserver</h3>
 213                                                 <p>In your email program's menu, select OpenPGP &rarr; Key Management.</p>
 214 <p>Right click on your key and select Upload Public Keys to Keyserver. Use the default keyserver in the popup.</p>
 215 <p class="notes">Now someone who wants to send you an encrypted message can download your public key from the Internet. There are multiple keyservers that you can select from the menu when you upload, but they are all copies of each other, so it doesn't matter which one you use. However, it sometimes takes a few hours for them to match each other when a new key is uploaded.</p>
 216                                                 <!-- ~~~~~~~~~ Solución de problemas  ~~~~~~~~~ -->
 217                                                 <div class="troubleshooting">
 218                                                         <h4>Solución de problemas</h4>
 219                                                         <dl>
 220                                                                 <dt>The progress bar never finishes</dt>
 221                                                                                 <dd>Close the upload popup, make sure you are on the Internet and try again. If that doesn't work, try again, selecting a different keyserver.</dd>
 222 <dt>My key doesnt appear in the list</dt>
 223                                                                                 <dd>Try checking Show Default Keys.</dd>
 224
 225                                                                 <dt class="feedback">Don't see a solution to your problem?</dt>
 226                                                                         <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
 227
 228                                                         </dl>
 229                                                 </div><!-- /.troubleshooting -->
 230                                         </div><!-- End .main -->
 231                                 </div><!-- End #step-2a .step  -->
 232                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 233                                 <div id="terminology" class="step">
 234                                         <div class="main">
 235                                                 <h3>GnuPG, OpenPGP, what?</h3>
 236                                                 <p>You're using a program called GnuPG, but the menu in your email program is called OpenPGP. Confusing, right? In general, the terms GnuPG, GPG, GNU Privacy Guard, OpenPGP and PGP are used interchangeably, though they all have slightly different meanings.</p>
 237                                         </div><!-- End .main -->
 238                                 </div><!-- End #terminology.step-->
 239
 240
 241                         </div>
 242                 </section><!-- End #section2 -->
 243
 244 <!-- ~~~~~~~~~ Section 3: Try it out  ~~~~~~~~~ -->
 245                 <section class="row" id="section3">
 246                         <div>
 247                                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 248                                 <div class="section-intro">
 249                                                 <h2><em>#3</em> Try it out!</h2>
 250                                                 <p>Now you'll try a test correspondence with a computer program named Adele, which knows how to use encryption. Except where noted, these are the same steps you'd follow when corresponding with a real, live person.</p>
 251                                 </div><!-- End .section-intro -->
 252
 253                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 254                                 <div id="step-3a" class="step">
 255                                         <div class="sidebar">
 256                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section3-try-it-out.png" alt="Try it out." /></p>
 257                                         </div><!-- /.sidebar -->
 258                                         <div class="main">
 259                                                 <h3><em>Step 3.a</em> Send Adele your public key</h3>
 260                                                 <p>This is a special step that you won't have to do when corresponding with real people. In your email program's menu, go to OpenPGP &rarr; Key Management. You should see your key in the list that pops up. Right click on your key and select Send Public Keys by Email. This will create a new draft message, as if you had just hit the Write button.</p>
 261
 262 <p>Address the message to adele-en@gnupp.de. Put at least one word (whatever you want) in the subject and body of the email, then hit send.</p>
 263
 264 <p class="notes">It may take two or three minutes for Adele to respond. In the meantime, you might want to skip ahead and check out the <a href="#section5">Use it Well</a> section of this guide. Once she's responded, head to the next step. From here on, you'll be doing just the same thing as when corresponding with a real person.</p>
 265                                         </div><!-- End .main -->
 266                                 </div><!-- End #step-3b .step -->
 267
 268                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 269                                 <div id="step-3b" class="step">
 270                                         <div class="main">
 271                                                         <h3><em>Step 3.b</em> Send a test encrypted email</h3>
 272                                                         <p>Write a new email in your email program, addressed to adele-en@gnupp.de. Make the subject "Encryption test" or something similar and write something in the body. Don't send it yet.</p>
 273                                                         <p>Click the icon of the key in the bottom right of the composition window (it should turn yellow). This tells Enigmail to encrypt the email with the key you downloaded in the last step.</p>
 274                                                         <p class="notes">Next to the key, you'll notice an icon of a pencil. Clicking this tells Enigmail to add a special, uniqe signature to your message, generated using your private key. This is a separate feature from encryption, and you don't have to use it for this guide.</p>
 275                                                         <p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>
 276
 277                                                         <p>To encrypt and email to Adele, you need her public key, and so now you'll have Enigmail download it from a keyserver. Click Download Missing Keys and use the default in the pop-up that asks you to choose a keyserver. Once it finds keys, check the first one (Key ID starting with 9), then select ok. Select ok in the next pop-up.</p>
 278
 279                                                         <p>Now you are back at the "Recipients not valid, not trusted or not found" screen. Select Adele's key from the list and click Ok. If the message doesn't send automatically, you can hit send now.</p>
 280                                         <!-- ~~~~~~~~~ Solución de problemas  ~~~~~~~~~ -->
 281                                                         <div class="troubleshooting">
 282                                                                 <h4>Solución de problemas</h4>
 283                                                                 <dl>
 284                                                                         <dt>Enigmail can't find Adele's key</dt>
 285                                                                                 <dd>Close the pop-ups that have appeared since you clicked. Make sure you are connected to the Internet and try again. If that doesn't work, repeat the process, choosing a different keyserver when it asks you to pick one.</dd>
 286                                                                 <dt class="feedback">Don't see a solution to your problem?</dt>
 287                                                                         <dd class="feedback">Please let us know on the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">feedback page</a>.</dd>
 288                                                                 </dl>
 289                                                         </div><!-- /.troubleshooting -->
 290                                                 </div><!-- End .main -->
 291                                         </div><!-- End #step-3b .step -->
 292
 293                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 294                                 <div id="step-headers_unencrypted" class="step">
 295                                         <div class="main">
 296                                                 <h3><em>Important:</em> Security tips</h3>
 297                                                 <p>Even if you encrypted your email, the subject line is not encrypted, so don't put private information there. The sending and receiving addresses aren't encrypted either, so they could be read by a surveillance system. When you send attachments, Enigmail will give you an option of whether you want to encrypt them.</p>
 298 <p>It's also good practice to click the key icon in your email composition window <strong>before</strong> you start to write. Otherwise, your email client could save an unencrypted draft on the mail server, potentially exposing it to snooping.</p>
 299                                         </div><!-- End .main -->
 300                                 </div><!-- End #step-headers_unencrypted .step-->
 301
 302
 303                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 304                                 <div id="step-3c" class="step">
 305                                         <div class="main">
 306                                                 <h3><em>Step 3.c</em> Receive a response</h3>
 307                                                 <p>When Adele receives your email, she will use her private key to decrypt it, then fetch your public key from a keyserver and use it to encrypt a response to you.</p>
 308                                                 <p class="notes">Since you encrypted this email with Adele's public key, Adele's private key is required to decrypt it. Adele is the only one with her private key, so no one except her &mdash; not even you &mdash; can decrypt it.</p>
 309                                                 <p class="notes">It may take two or three minutes for Adele to respond. In the meantime, you might want to skip ahead and check out the <a href="#section5">Use it Well</a> section of this guide.</p>
 310                                                 <p>When you receive Adele's email and open it, Enigmail will automatically detect that it is encrypted with your public key, and then it will use your private key to decrypt it.</p>
 311                                                 <p>Notice the bar that Enigmail shows you above the message, with information about the status of Adele's key.</p>
 312                                         </div><!-- End .main -->
 313                                 </div><!-- End #step-3c .step -->
 314
 315 <!-- STEP 3D IS COMMENTED OUT UNTIL WE FIND A WAY TO VALIDATE SIGNATURES
 316                                 <div id="step-3d" class="step">
 317                                         <div class="main">
 318                                                 <h3><em>Step 3.d</em> Send a test signed email to a friend</h3>
 319                                                 <p>Write a new email in your email program, addressed to a friend. If you want, tell them about this guide!</p>
 320                                                 <p>Before sending the email, click the icon of the pencil in the bottom right of the composition window (it should turn yellow). This tells Enigmail to sign the email with you private key.</p>
 321                                                 <p>After you click send, Enigmail will ask you for your password. It will do this any time it needs to use your public key.</p>
 322                                         </div>
 323                                 </div>-->
 324                         </div>
 325                 </section><!-- End #section3 -->
 326
 327
 328 <!-- ~~~~~~~~~ Section 4: Learn the Web of Trust  ~~~~~~~~~ -->
 329                 <section class="row" id="section4">
 330                         <div>
 331                                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 332                                 <div class="section-intro">
 333                                                 <h2><em>#4</em> Learn the Web of Trust</h2>
 334                                                 <p>Email encryption is a powerful technology, but it has a weakness; it requires a way to verify that a person's public key is actually theirs. Otherwise, there would be no way to stop an attacker from making an email address with your friend's name, creating keys to go with it and impersonating your friend. That's why the free software programmers that developed email encryption created keysigning and the Web of Trust.</p>
 335
 336 <p>When you sign someone's key, you are publicly saying that you trust that it does belong to them and not an impostor. People who use your public key can see the number of signatures it has. Once you've used GnuPG for a long time, you may have hundreds of signatures. The Web of Trust is the constellation of all GnuPG users, connected to each other by chains of trust expressed through signatures, into a giant network. The more signatures a key has, and the more signatures its signers' keys have, the more trustworthy that key is.</p>
 337
 338 <p>People's public keys are usually identified by their key fingerprint, which is a string of digits like DD878C06E8C2BEDDD4A440D3E573346992AB3FF7 (for Adele's key). You can see the fingerprint for your public key, and other public keys saved on your computer, by going to OpenPGP &rarr; Key Management in your email program's menu, then right clicking on the key and choosing Key Properties. It's good practice to share your fingerprint wherever you share your email address, so that so that people can double-check that they have the correct public key when they download yours from a keyserver.</p>
 339
 340 <p class="notes">You may also see public keys referred to by their key ID, which is simply the last 8 digits of the fingerprint, like 92AB3FF7 for Adele. The key ID is visible directly from the Key Management Window. This key ID is like a person's first name (it is a useful shorthand but may not be unique to a given key), whereas the fingerprint actually identifies the key uniquely without the possibility of confusion. If you only have the key ID, you can still look up the key (as well as its fingerprint), like you did in Step 3, but if multiple options appear, you'll need the fingerprint of the person to are trying to communicate to verify which one to use.</p>
 341
 342
 343                                 </div><!-- End .section-intro -->
 344
 345                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 346                                 <div id="step-4a" class="step">
 347                                         <div class="sidebar">
 348                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust" /></p>
 349                                         </div><!-- /.sidebar -->
 350                                         <div class="main">
 351                                                 <h3><em>Step 4.a</em> Sign a key</h3>
 352                                                 <p>In your email program's menu, go to OpenPGP &rarr; Key Management.</p>
 353                                                 <p>Right click on Adele's public key and select Sign Key from the context menu.</p>
 354                                                 <p>In the window that pops up, select "I will not answer" and click OK.</p>
 355                                                 <p>In your email program's menu, go to OpenPGP &rarr; Key Management &rarr; Keyserver &rarr; Upload Public Keys and hit OK.</p>
 356                                                 <p class="notes">You've just effectively said "I trust that Adele's public key actually belongs to Adele." This doesn't mean much because Adele isn't a real person, but it's good practice.</p>
 357
 358
 359                                                 <!--<div id="pgp-pathfinder">
 360                                                         <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">
 361                                                                 <p><strong>From:</strong> <input type="text" placeholder="xD41A008"  name="FROM"></p>
 362                                                                 <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>
 363                                                                 <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>
 364                                                         </form>
 365                                                 </div><!-- End #pgp-pathfinder -->
 366
 367                                         </div><!-- End .main -->
 368                                 </div><!-- End #step-4a .step -->
 369                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 370                                 <div id="step-sign_real_keys" class="step">
 371                                         <div class="main">
 372                                                 <h3><em>Important:</em> check people's identification before signing their keys</h3>
 373                                                 <p>Before signing a real person's key, always make sure it actually belongs to them, and that they are who they say they are. Ask them to show you their ID (unless you trust them very highly) and their public key fingerprint -- not just the shorter public key ID, which could refer to another key as well. In Enigmail, answer honestly in the window that pops up and asks "How carefully have you verified that the key you are about to sign actually belongs to the person(s) named above?".</p>
 374                                         </div><!-- End .main -->
 375                                 </div><!-- End #step-sign_real_keys .step-->
 376
 377
 378
 379                         </div>
 380                 </section><!-- End #section4 -->
 381
 382 <!-- ~~~~~~~~~ Section 5: Use it well  ~~~~~~~~~ -->
 383                 <section id="section5" class="row">
 384                         <div>
 385                                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 386                                 <div class="section-intro">
 387                                                 <h2><em>#5</em> Use it well</h2>
 388 <p>Everyone uses GnuPG a little differently, but it's important to follow some basic practices to keep your email secure. Not following them, you risk the privacy of the people you communicate with, as well as your own, and damage the Web of Trust.</p>
 389                                 </div><!-- End .section-intro -->
 390
 391                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 392                                 <div id="step-5a" class="step">
 393                                         <div class="sidebar">
 394                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section5-01-use-it-well.png" alt="Section 5: Use it Well" /></p>
 395                                         </div><!-- /.sidebar -->
 396                                         <div class="main">
 397                                                 <h3>When should I encrypt?</h3>
 398
 399                                                 <p>The more you can encrypt your messages, the better. This is because, if you only encrypt emails occasionally, each encrypted message could raise a red flag for surveillance systems. If all or most of your email is encrypted, people doing surveillance won't know where to start.</p>
 400
 401 <p>That's not to say that only encrypting some of your email isn't helpful -- it's a great start and it makes bulk surveillance more difficult.</p>
 402
 403                                         </div><!-- End .main -->
 404                                 </div><!-- End #step-5a .step -->
 405
 406                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 407                                 <div id="step-5b" class="step">
 408                                         <div class="sidebar">
 409                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well" /></p>
 410                                         </div><!-- /.sidebar -->
 411                                         <div class="main">
 412                                                 <h3><em>Important:</em> Be wary of invalid keys</h3>
 413                                                 <p>GnuPG makes email safer, but it's still important to watch out for invalid keys, which might have fallen into the wrong hands. Email encrypted with invalid keys might be readable by surveillance programs.</p>
 414                                                 <p>In your email program, go back to the second email that Adele sent you. Because Adele encrypted it with your public key, it will have a message from OpenPGP at the top, which most likely says "OpenPGP: Part of this message encrypted."</p>
 415 <p><b>When using GnuPG, make a habit of glancing at that bar. The program will warn you there if you get an email encrypted with a key that can't be trusted.</b></p>
 416                                         </div><!-- End .main -->
 417                                 </div><!-- End #step-5b .step -->
 418
 419                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 420                                 <div id="step-5c" class="step">
 421                                         <div class="main">
 422                                                 <h3>Copy your revocation certificate to somewhere safe</h3>
 423                                                 <p>Remember when you created your keys and saved the revocation certificate that GnuPG made? It's time to copy that certificate onto the safest digital storage that you have -- the ideal thing is a flash drive, disk or hard drive stored in a safe place in your home.</p>
 424 <p>If your private key ever gets lost or stolen, you'll need this certificate file.</p>
 425                                         </div><!-- End .main -->
 426                                 </div><!-- End #step-5c .step -->
 427
 428                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 429                                 <div id="step-lost_key" class="step">
 430                                         <div class="main">
 431                                                 <h3><em>Important:</em> act swiftly if someone gets your private key</h3>
 432                                                 <p>If you lose your private key or someone else gets ahold of it (say, by stealing or cracking your computer), it's important to revoke it immediately before someone else uses it to read your encrypted email. This guide doesn't cover how to revoke a key, but you can follow the <a href="https://www.gnupg.org/gph/en/manual.html#AEN305">instructions on the GnuPG site</a>. After you're done revoking, send an email to everyone with whom you usually use your key to make sure they know.</p>
 433                                         </div><!-- End .main -->
 434                                 </div><!-- End #step-lost_key .step-->
 435
 436                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~
 437                                 <div id="step-5d" class="step">
 438                                         <div class="main">
 439                                                 <h3>Make your public key part of your online identity</h3>
 440                                                 <p> First add your public key fingerprint to your email signature, then compose an email to at least five of your friends, telling them you just set up GnuPG and mentioning your public key fingerprint. Link to this guide and ask them to join you. Don't forget that there's also an awesome <a href="infographic.html">infographic to share.</a></p>
 441
 442 <p class="notes">Start writing your public key fingerprint anywhere someone would see your email address: your social media profiles, blog, Website, or business card. (At the Free Software Foundation, we put ours on our <a href="https://fsf.org/about/staff">staff page</a>.) We need to get our culture to the point that we feel like something is missing when we see an email address without a public key fingerprint.</p>
 443                                         </div><!-- End .main
 444                                 </div> End #step-5d .step-->
 445
 446
 447                         </div>
 448                 </section><!-- End #section5 -->
 449
 450
 451
 452 <!-- ~~~~~~~~~ Section 6: Next steps  ~~~~~~~~~ -->
 453                 <section class="row" id="section6">
 454                         <div id="step-click_here" class="step">
 455                                         <div class="main">
 456                                           <h2><a href="next_steps.html">Click here when you're done</a></h2>
 457
 458                                         </div><!-- End .main -->
 459                                 </div><!-- End #step-click_here .step-->
 460
 461                 </section><!-- End #section6 -->
 462
 463 <!-- ~~~~~~~~~ FAQ  ~~~~~~~~~ -->
 464 <!-- When un-commenting this section go to main.css and search
 465                 for /* Guide Sections Background */ then add #faq to the desired color
 466
 467                 <section class="row" id="faq">
 468                         <div>
 469                                 <div class="sidebar">
 470                                         <h2>FAQ</h2>
 471                                 </div>
 472
 473                                 <div class="main">
 474                                         <dl>
 475                                                 <dt>My key expired</dt>
 476                                                         <dd>Answer coming soon.</dd>
 477
 478                                                 <dt>Who can read encrypted messages? Who can read signed ones?</dt>
 479                                                         <dd>Answer coming soon.</dd>
 480
 481                                                 <dt>My email program is opening at times I don't want it to open/is now my default program and I don't want it to be.</dt>
 482                                                         <dd>Answer coming soon.</dd>
 483                                         </dl>
 484                                 </div>
 485                         </div>
 486                 </section> --><!-- End #faq -->
 487
 488 <!-- ~~~~~~~~~ Footer  ~~~~~~~~~ -->
 489                 <footer class="row" id="footer">
 490                         <div>
 491                                 <div id="copyright">
 492                                         <h4><a href="https://u.fsf.org/ys"><img alt="Free Software Foundation" src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png"></a></h4>
 493                                         <p>Copyright &copy; 2014 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. <a href="https://u.fsf.org/yr">Join.</a></p>
 494                                         <p><em>Version 2.0, launched 6/18/2014. <!--LANGUAGE translation by NAME, NAME and NAME.--></em></p>
 495 <p>The images on this page are under a <a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 license (or later version)</a>, and the rest of it is under a <a href="https://creativecommons.org/licenses/by-sa/4.0">Creative Commons Attribution-ShareAlike 4.0 license (or later version)</a>. &mdash; <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>
 496                                         <p>Download the source packages for <a href="gnupg-guide.zip">this guide</a> and for <a href="gnupg-infographic.zip">the infographic</a>. Fonts used in the guide &amp; infographic: <a href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> by Pablo Impallari, <a href="http://www.google.com/fonts/specimen/Signika">Signika</a> by Anna Giedry&#347; <a href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> by Omnibus-Type, <a href="http://www.thegopherarchive.com/gopher-files-hacks-pxl2000-119351.htm">PXL-2000</a> by Florian Cramer.</p>
 497                                         <p>
 498                                           <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
 499                                              rel="jslicense">
 500                                             JavaScript license information
 501                                           </a>
 502                                         </p>
 503                                 </div><!-- /#copyright -->
 504                                 <p class="credits">
 505                                         Infographic and guide design by <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong> <img src="//static.fsf.org/nosvn/enc-dev0n/img/jplusplus.png" alt="Journalism++" /></a>
 506                                 </p><!-- /.credits -->
 507                         </div>
 508                 </footer><!-- End #footer -->
 509
 510                 <script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
 511                 <script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
 512
 513                 <!-- Piwik -->
 514                 <script type="text/javascript">
 515                  /*
 516                  @licstart The following is the entire license notice for the
 517                     JavaScript code in this page.
 518
 519                  Copyright 2014 Matthieu Aubry
 520
 521                   This program is free software: you can redistribute it and/or modify
 522                  it under the terms of the GNU General Public License as published by
 523                  the Free Software Foundation, either version 3 of the License, or
 524                  (at your option) any later version.
 525
 526                   This program is distributed in the hope that it will be useful,
 527                  but WITHOUT ANY WARRANTY; without even the implied warranty of
 528                  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 529                  GNU General Public License for more details.
 530
 531                   You should have received a copy of the GNU General Public License
 532                  along with this program.  If not, see http://www.gnu.org/licenses/.
 533
 534                   @licend The above is the entire license notice
 535                      for the JavaScript code in this page.
 536                  */
 537                  var _paq = _paq || [];
 538                  _paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
 539                  _paq.push(["setCookieDomain", "*.www.fsf.org"]);
 540                  _paq.push(["setDomains", ["*.www.fsf.org","*.www.fsf.org"]]);
 541                  _paq.push(["trackPageView"]);
 542                  _paq.push(["enableLinkTracking"]);
 543
 544                  (function() {
 545                    var u=(("https:" == document.location.protocol) ? "https" : "http") + "://piwik.fsf.org/";
 546                    _paq.push(["setTrackerUrl", u+"piwik.php"]);
 547                    _paq.push(["setSiteId", "5"]);
 548                    var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
 549                    g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
 550                  })();
 551                 </script>
 552                 <!-- End Piwik Code -->
 553         </body>
 554 </html>