es/workshops.html

   1 <html><head>
   2         <meta http-equiv="content-type" content="text/html; charset=utf-8">
   3
   4         <title>Defensa personal de correo electrónico - ¡Enseña a tus amigos!</title>
   5         <meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy, email, Enigmail">
   6         <meta name="description" content="Email surveillance violates our fundamental rights and makes free speech risky. This guide will teach you email self-defense in 30 minutes with GnuPG.">
   7
   8         <meta name="viewport" content="width=device-width, initial-scale=1">
   9         <link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css">
  10         <link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico">
  11
  12 </head>
  13 <body>
  14         <!-- Fundraiser banner -->
  15         <iframe id="topbanner" src="//static.fsf.org/nosvn/banners/2015fundraiser/2015-fundraiser-banner-no-js.html" width="100%" height="180px" frameborder="0"></iframe>
  16         <!-- End fundraiser banner
  17
  18         <!-- ~~~~~~~~~ GnuPG Header and introduction text  ~~~~~~~~~ -->
  19
  20         <header class="row" id="header">
  21                 <div>
  22                         <h1>Defensa personal del correo electrónico</h1>
  23
  24                         <!-- Languages removed until we have translations-->
  25
  26                         <ul id="menu" class="os">
  27                                 <li class="spacer">
  28                                         <a href="index.html">GNU/Linux</a>
  29                                 </li>
  30                                 <li>
  31                                         <a href="mac.html">Mac OS</a>
  32                                 </li>
  33                                 <li>
  34                                         <a href="windows.html">Windows</a>
  35                                 </li>
  36                                 <li class="spacer"><a href="workshops.html" class="current">Enseña a tus amigos</a></li>
  37                                 <li class="spacer">
  38                                         <a href="https://fsf.org/share?u=https://u.fsf.org/zb&amp;t=Email encryption for everyone via %40fsf">
  39                                                 Share&nbsp;
  40                                                 <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png" class="share-logo" alt="[GNU Social]">&nbsp;
  41                                                 <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png" class="share-logo" alt="[Pump.io]">&nbsp;
  42                                                 <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png" class="share-logo" alt="[Reddit]">&nbsp;
  43                                                 <img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png" class="share-logo" alt="[Hacker News]">
  44                                         </a>
  45                                 </li>
  46                         </ul>
  47                         <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
  48                         <div id="fsf-intro">
  49                                 <h3>
  50                                         <a href="http://u.fsf.org/ys">
  51                                                 <img alt="Free Software Foundation" src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png">
  52                                         </a>
  53                                 </h3>
  54                                 <div class="fsf-emphasis">
  55                                         <p>
  56                                                         Queremos traducir esta guía
  57                                                         a más idiomas, y hacer una versión para cifrado en dispositivos
  58                                                         móviles. Por favor haga una donación y ayude a usuarios de todo el mundo
  59                                                         a dar sus primeros pasos hacia la privacidad de su privacidad con software libre.
  60                                         </p>
  61                                 </div>
  62
  63                                 <p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&amp;id=14&amp;pk_campaign=email_self_defense&amp;pk_kwd=guide_donate"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png"></a>  </p>
  64
  65                         </div><!-- End #fsf-intro -->
  66
  67                         <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
  68                         <div class="intro">
  69                                 <p>
  70                                         <a id="infographic" href="https://emailselfdefense.fsf.org/en/infographic.html"><img src="//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png" alt="View &amp; share our infographic →"></a>
  71                                 </p><p>Comprender y establecer un cifrado en el correo electrónico parece una tarea abrumadora para mucha gente. Por este motivo ayudar a tus amigos con GnuPG es una tarea importante para ayudar a difundir el cifrado. Incluso si se trata de hacerlo a una sola persona, eso incluso es una persona más que usará el cifrado y que antes no lo estaba haciendo. Tienes la capacidad de ayudar a tus amigos a mantener sus cartas digitales de amor en privado, y enseñarles sobre la importancia del software libre. Si utilizas GnuPG para mandar y recibir correo cifrado, ¡eres un perfecto candidato para llevar a cabo un taller!</p>
  72
  73                         </div><!-- End .intro -->
  74
  75                 </div>
  76         </header><!-- End #header -->
  77
  78         <!-- ~~~~~~~~~ Section 1: Get your friends or community interested>  ~~~~~~~~~ -->
  79         <section style="padding-top: 0px;" class="row" id="section1">
  80                 <div style="padding-top: 0px;">
  81
  82                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
  83                         <div class="section-intro">
  84                                 <p style="margin-top: 0px;" class="image"><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/workshop-section1.png"></p>
  85                                 <h2><em>#1</em> Consiga que sus amigos o comunidad se interesen </h2>
  86                                 <p>Si ha escuchado a sus amigos quejarse por su falta de privacidad, pregúnteles si están interesados en acudir a un taller sobre defensa personal del correo electrónico. Si sus amigos no se quejan sobre su privacidad entonces quizás necesiten un poco de convencimiento. Quizás incluso haya oido el clásico argumento contra el cifrado "si no tienes nada que ocultar, no tienes nada que temer".</p>
  87                                 <p>Aquí hay algunos temas de conversación que puedes utilizar para explicar porque merece la pena aprender sobre GnuPG Here are some talking points you can use to help explain why it's worth it to learn GnuPG. Mezcle y combine aquello que cree que tendrá sentido en su comunidad:</p>
  88
  89                         </div><!-- End .section-intro -->
  90
  91                         <div id="step-aa" class="step">
  92
  93
  94                                 <div class="sidebar">
  95 <!-- Workshops image commented out from here, to be used above instead.
  96                                         <p><img id="workshops-image" src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/workshop-section1.png" alt="Workshop icon"></p>-->
  97                                 </div><!-- /.sidebar -->
  98
  99                                 <div class="main">
 100                                         <h3>La fuerza de las cifras</h3>
 101                                         <p>Cada persona que resiste a la vigilancia masiva hace más sencillo que otros también resistan. Gente normalizando el uso de un cifrado robusto provoca múltiples efectos de gran alcance: significa que aquellos que más necesitan privacidad, como potenciales confidentes y activistas, tienen mayor probabilidad a aprender sobre el cifrado. Cuanta más gente utilice el cifrado para más cosas esto también hace difícil para los sistemas de vigilancia el poder señalar a quellos que no pueden permitirse el lujo de ser encontrados, y muestra su solidaridad con esa gente.</p>
 102                                 </div><!-- End .main -->
 103
 104                                 <div class="main">
 105                                         <h3>Gente que respetas puede ya estar usando el cifrado</h3>
 106                                         <p>Muchos periodistas, confidentes, activistas e investigadores utilizan GnuPG, por lo que sus amigos sin saberlo, podrían haber oído hablar de unas cuantas personas que ya lo utilizan. Puede realizar una búsqueda de "BEGIN PUBLIC KEY BLOCK" + una_palabra_clave para ayudarle a realizar una lista con gente u organizaciones que utilizan GnuPG a quienes su comunidad probablemente reconocerán.</p>
 107                                 </div><!-- End .main -->
 108
 109                                 <div class="main">
 110                                         <h3>Respeta la privacidad de tus amigos</h3>
 111                                         <p>No hay una manera objetiva de judgar qué es lo que constituye una correspondencia de caracter privado. Por ello es mejor no suponer que sólo porque encuentras que un correo electrónico que mandaste a un amigo es intrascendental, tu amigo (o un agente de vigilancia, ¡por eso importa!) siente de la misma manera. Muestra respeto a tus amigos cifrando tu correspondencia con ellos.</p>
 112                                 </div><!-- End .main -->
 113
 114
 115                                 <div class="main">
 116                                         <h3>La privacidad tecnológica es normal en el mundo físico</h3>
 117                                         <p>En el campo de lo físico, tenemos persianas, sobres, y puertas cerradas para garantizarnos formas de proteger nuestra privacidad. ¿Por qué deberíam haber en el campo digital alguna diferencia?</p>
 118                                 </div><!-- End .main -->
 119
 120                                 <div class="main">
 121                                         <h3>No deberíamos confiar a nuestros proveedores de correo electrónico nuestra privacidad</h3>
 122                                         <p>Algunos proveedores de correo electrónico son muy dignos de confianza, pero pueden tener incentivos para no proteger nuestra privacidad y seguridas. Para ser ciudadanos digitales conscientes, necesitamos construir nuestra propia seguridad desde la base.</p>
 123                                 </div><!-- End .main -->
 124
 125
 126                         </div><!-- End #step-2a .step -->
 127
 128                 </div>
 129         </section><!-- End #section1 -->
 130
 131         <!-- ~~~~~~~~~ Section 2: Plan The Workshop  ~~~~~~~~~ -->
 132         <section class="row" id="section2">
 133                 <div>
 134                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 135                         <div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
 136                                 <h2><em>#2</em> Plan The Workshop</h2>
 137                                 <p>Once you've got at least one interested friend, pick a date and start planning out the workshop. Tell participants to bring their computer and ID (for signing each other's keys). If you'd like to make it easy for the participants to use Diceware for choosing passwords, get a pack of dice beforehand. Make sure the location you select has an easily accessible Internet connection, and make backup plans in case the connection stops working on the day of the workshop. Libraries, coffee shops, and community centers make great locations. Try to get all the participants to set up an Enigmail-compatible email client before the event. Direct them to their email provider's IT department or help page if they run into errors.</p><p>
 138                                 </p><p>Estimate that the workshop will take at least forty minutes plus ten minutes for each participant. Plan extra time for questions and technical glitches.</p>
 139                                 <p>The success of the workshop requires understanding and catering to the unique backgrounds and needs of each group of participants. Workshops should stay small, so that each participant receives more individualized instruction. If more than a handful of people want to participate, keep the facilitator to participant ratio high by recruiting more facilitators, or by facilitating multiple workshops. Small workshops among friends work great!</p>
 140
 141
 142                         </div><!-- End .section-intro -->
 143
 144                 </div>
 145         </section><!-- End #section2 -->
 146
 147         <!-- ~~~~~~~~~ Section 3: Follow The Guide  ~~~~~~~~~ -->
 148         <section class="row" id="section3">
 149                 <div>
 150                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 151                         <div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
 152                                 <h2><em>#3</em> Follow the guide as a group</h2>
 153                                 <p>Work through the Email Self-Defense guide a step at a time as a group. Talk about the steps in detail, but make sure not to overload the participants with minutia. Pitch the bulk of your instructions to the least tech-savvy participants. Make sure all the participants complete each step before the group moves on to the next one. Consider facilitating secondary workshops afterwards for people that had trouble grasping the concepts, or those that grasped them quickly and want to learn more.</p>
 154                                 <p>In <a href="index.html#section2">Section 2</a> of the guide, make sure the participants upload their keys to the same keyserver so that they can immediately download each other's keys later (sometimes there is a delay in synchronization between keyservers). During <a href="index.html#section3">Section 3</a>, give the participants the option to send test messages to each other instead of or as well as Edward. Similarly, in <a href="index.html#section4">Section 4</a>, encourage the participants to sign each other's keys. At the end, make sure to remind people to safely back up their revocation certificates.</p>
 155
 156                         </div><!-- End .section-intro -->
 157                 </div>
 158         </section>
 159
 160
 161         <!-- ~~~~~~~~~ Section 4: Explain the pitfalls  ~~~~~~~~~ -->
 162         <section class="row" id="section4">
 163                 <div>
 164                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 165                         <div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
 166                                 <h2><em>#4</em> Explain the pitfalls</h2>
 167                                 <p>Remind participants that encryption works only when it's explicitly used; they won't be able to send an encrypted email to someone who hasn't already set up encryption. Also remind participants to double-check the encryption icon before hitting send, and that subjects and timestamps are never encrypted.</p>
 168                                 <p> Explain the <a href="https://www.gnu.org/proprietary/proprietary.html">dangers of running a proprietary system</a> and advocate for free software, because without it, we can't <a href="https://www.fsf.org/bulletin/2013/fall/how-can-free-software-protect-us-from-surveillance">meaningfully resist invasions of our digital privacy and autonomy</a>.</p>
 169
 170
 171
 172                         </div><!-- End .section-intro -->
 173
 174                 </div>
 175         </section><!-- End #section4 -->
 176
 177         <!-- ~~~~~~~~~ Section 5: Explain The Pitfalls  ~~~~~~~~~ -->
 178         <section id="section5" class="row">
 179                 <div>
 180                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 181                         <div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
 182                                 <h2><em>#5</em> Share additional resources</h2>
 183                                 <p>GnuPG's advanced options are far too complex to teach in a single workshop. If participants want to know more, point out the advanced subsections in the guide and consider organizing another workshop. You can also share <a href="https://www.gnupg.org/documentation/index.html">GnuPG's</a> and <a href="https://www.enigmail.net/documentation/index.php">Enigmail's</a> official documentation and mailing lists. Many GNU/Linux distribution's Web sites also contain a page explaining some of GnuPG's advanced features.</p>
 184
 185                         </div><!-- End .section-intro -->
 186
 187
 188                 </div>
 189         </section><!-- End #section5 -->
 190
 191
 192
 193         <!-- ~~~~~~~~~ Section 6: Next steps  ~~~~~~~~~ -->
 194         <section class="row" id="section6">
 195                 <div>
 196                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 197                         <div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
 198                                 <h2><em>#6</em> Follow up</h2>
 199                                 <p>Make sure everyone has shared email addresses and public key fingerprints before they leave. Encourage the participants to continue to gain GnuPG experience by emailing each other. Send them each an encrypted email one week after the event, reminding them to try adding their public key ID to places where they publicly list their email address.</p>
 200                                 <p>If you have any suggestions for improving this workshop guide, please let us know at <a href="mailto:campaigns@fsf.org">campaigns@fsf.org</a>.</p>
 201
 202                         </div><!-- End .section-intro -->
 203
 204
 205                 </div>
 206         </section><!-- End #section6 -->
 207
 208         <!-- ~~~~~~~~~ FAQ  ~~~~~~~~~ -->
 209         <!-- When un-commenting this section go to main.css and search
 210         for /* Guide Sections Background */ then add #faq to the desired color
 211
 212         <section class="row" id="faq">
 213         <div>
 214         <div class="sidebar">
 215         <h2>FAQ</h2>
 216 </div>
 217
 218 <div class="main">
 219 <dl>
 220 <dt>My key expired</dt>
 221 <dd>Answer coming soon.</dd>
 222
 223 <dt>Who can read encrypted messages? Who can read signed ones?</dt>
 224 <dd>Answer coming soon.</dd>
 225
 226 <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>
 227 <dd>Answer coming soon.</dd>
 228 </dl>
 229 </div>
 230 </div>
 231 </section> --><!-- End #faq -->
 232
 233 <!-- ~~~~~~~~~ Footer  ~~~~~~~~~ -->
 234                 <footer class="row" id="footer">
 235                         <div>
 236                                 <div id="copyright">
 237                                         <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>
 238                                         <p>Copyright &copy; 2014-2016 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please support our work by <a href="https://u.fsf.org/yr">joining us as an associate member.</a></p>
 239
 240 <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>. Download the <a href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">source code of Edward reply bot</a> by Andrew Engelbrecht &lt;sudoman@ninthfloor.org&gt; and Josh Drake &lt;zamnedix@gnu.org&gt;, available under the GNU Affero General Public License. <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>
 241
 242 <p>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="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a> by Florian Cramer.</p>
 243
 244 <p>Download the <a href="emailselfdefense_source.zip">source package</a> for this guide, including fonts, image source files and the text of Edward's messages.</p>
 245
 246 <p>This site uses the Weblabels standard for labeling <a href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View the JavaScript <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/" rel="jslicense">source code and license information</a>.</p>
 247                                 </div><!-- /#copyright -->
 248                                 <p class="credits">
 249                                         Infographic and guide design by <a rel="external" href="http://jplusplus.org"><strong>Journalism++</strong> <img src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png" alt="Journalism++" /></a>
 250                                 </p><!-- /.credits -->
 251                         </div>
 252                 </footer><!-- End #footer -->
 253 <script src="http://piwik.fsf.org/piwik.js" async="" defer="" type="text/javascript"></script><script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
 254 <!--            <script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script> -->
 255
 256 <!-- Piwik -->
 257 <script type="text/javascript">
 258         /*
 259         @licstart The following is the entire license notice for the
 260         JavaScript code in this page.
 261
 262         Copyright 2014 Matthieu Aubry
 263
 264         This program is free software: you can redistribute it and/or modify
 265         it under the terms of the GNU General Public License as published by
 266         the Free Software Foundation, either version 3 of the License, or
 267         (at your option) any later version.
 268
 269         This program is distributed in the hope that it will be useful,
 270         but WITHOUT ANY WARRANTY; without even the implied warranty of
 271         MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 272         GNU General Public License for more details.
 273
 274         You should have received a copy of the GNU General Public License
 275         along with this program.  If not, see http://www.gnu.org/licenses/.
 276
 277         @licend The above is the entire license notice
 278         for the JavaScript code in this page.
 279         */
 280         var _paq = _paq || [];
 281         _paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
 282         _paq.push(["setCookieDomain", "*.www.fsf.org"]);
 283         _paq.push(["setDomains", ["*.www.fsf.org","*.www.fsf.org"]]);
 284         _paq.push(["trackPageView"]);
 285         _paq.push(["enableLinkTracking"]);
 286
 287         (function() {
 288                 var u=(("https:" == document.location.protocol) ? "https" : "http") + "://piwik.fsf.org/";
 289                 _paq.push(["setTrackerUrl", u+"piwik.php"]);
 290                 _paq.push(["setSiteId", "5"]);
 291                 var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
 292                 g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
 293         })();
 294 </script>
 295 <!-- End Piwik Code -->
 296
 297
 298 </body></html>