en/workshops.html

   1 <!DOCTYPE html>
   2 <html>
   3         <head>
   4                         <meta http-equiv="content-type" content="text/html; charset=utf-8" />
   5
   6                         <title>Email Self-Defense - Teach your friends!</title>
   7                         <meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy, email, Enigmail" />
   8       <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." />
   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 <!-- Languages removed until we have translations-->
  24
  25                           <ul id="menu" class="os">
  26                             <li class="spacer">
  27                               <a href="index.html">GNU/Linux</a>
  28                             </li>
  29                             <li>
  30                               <a href="mac.html">Mac OS</a>
  31                             </li>
  32                             <li>
  33                               <a href="windows.html">Windows</a>
  34                             </li>
  35 <li class="spacer"><a href="workshops.html" class="current">Lead a Workshop</a></li>
  36                             <li class="spacer">
  37                               <a href="https://fsf.org/share?u=https://u.fsf.org/zb&amp;t=Email encryption for everyone via %40fsf">
  38                                  Share&nbsp;
  39                                 <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png"
  40                                      class="share-logo" alt="[GNU Social]">&nbsp;
  41                                  <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png"
  42                                       class="share-logo" alt="[Pump.io]">&nbsp;
  43                                  <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png"
  44                                       class="share-logo" alt="[Reddit]">&nbsp;
  45                                  <img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png"
  46                                       class="share-logo" alt="[Hacker News]">
  47                               </a>
  48                             </li>
  49                                                                                                                 <li class="spacer">V4.0</li>
  50                           </ul>
  51                                 <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
  52                                 <div id="fsf-intro">
  53                                   <h3>
  54                                     <a href="http://u.fsf.org/ys">
  55                                       <img alt="Free Software Foundation" src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png">
  56                                     </a>
  57                                   </h3>
  58                                   <div class="fsf-emphasis">
  59                                     <p>
  60                                       We fight for computer users'
  61 rights, and promote the development of free (as in freedom) software.
  62 Resisting bulk surveillance is very important to us.
  63                                     </p>
  64                                     <p>
  65                                       <strong>
  66                                         We want to translate this guide
  67 into more languages, and make a version for encryption on mobile
  68 devices. Please donate, and help people around the world take the first
  69 step towards protecting their privacy with free software.
  70                                       </strong>
  71                                     </p>
  72                                   </div>
  73
  74                                         <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>
  75
  76                                 </div><!-- End #fsf-intro -->
  77
  78                                 <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
  79                                 <div class="intro">
  80                                         <p>
  81                                                 <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>
  82                                         <p>Understanding and setting up email encryption sounds like a daunting task to many people. That's why helping your friends with GnuPG plays such an important role in helping spread encryption. Even if only one person shows up, that's still one more person using encryption who wasn't before. You have the power to help your friends keep their digital love letters private, and teach them about the importance of free software. If you use GnuPG to send and receive encrypted email, you're a perfect candidate for leading a workshop!</p>
  83
  84                                 </div><!-- End .intro -->
  85
  86                         </div>
  87                 </header><!-- End #header -->
  88
  89 <!-- ~~~~~~~~~ Section 1: Get your friends or community interested>  ~~~~~~~~~ -->
  90                 <section class="row" id="section1">
  91                         <div>
  92                                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
  93                                 <div class="section-intro">
  94                                                 <h2><em>#1</em> Get your friends or community interested </h2>
  95                                                 <p>If you hear friends grumbling about their lack of privacy, ask them if they're interested in attending a workshop on Email Self-Defense. If your friends don't grumble about privacy, they may need some convincing. You might even hear the classic "If you've got nothing to hide, you've got nothing to fear" argument against using encryption.</p>
  96                                                 <p>Here are some arguments you can use to help explain why it's worth it to learn GnuPG. Feel free to mix and match whichever you think will make sense to your community:</p>
  97
  98                                 </div><!-- End .section-intro -->
  99
 100                                 <div id="step-aa" class="step">
 101                                         <div class="main">
 102                                                 <h3><em>Step 1.a</em> Strength in numbers</h3>
 103                                                 <p>Each person who chooses to resist mass surveillance with encryption makes it easier for others to resist as well. People normalizing the use of strong cryptography has multiple powerful effects: It means those that truly need it, like potential whistle-blowers and activists, are more likely to learn about it. More people using it for more things also makes it harder for surveillance systems to single out those that can't afford to be found, and shows solidarity with those people.</p>
 104
 105                                         </div><!-- End .main -->
 106                                 </div><!-- End #step-2a .step -->
 107
 108                         </div>
 109                 </section><!-- End #section1 -->
 110
 111 <!-- ~~~~~~~~~ Section 1: Plan The Workshop  ~~~~~~~~~ -->
 112                 <section class="row" id="section2">
 113                         <div>
 114                                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 115                                 <div class="section-intro">
 116                                         <h2><em>#1</em> Plan The Workshop</h2>
 117                                                 <p>When you hear friends bemoaning their lack of digital privacy, ask them if they're interested in attending a workshop to on email self-defense. Once you've got a handful of people interested, pick a date and start planning out the event. Tell participants to bring their computer, their ID (for signing each other's key) and a flash drive.</p>
 118
 119 <p>The success of each workshop requires understanding and catering to the unique background and needs of each group of participants. Workshops should stay small, so that participants receive more individualized instruction. If more than a handful of people want to participate, keep the participant:facilitator ratio low by recruiting more facilitators, or by facilitating multiple workshops. Ideally, facilitators should be known and trusted members of the participants' community. Small workshops among friends work great!</p>
 120
 121 <p>Many activists, journalists, whistleblowers, businessfolk, academics, and dissidents use the OpenPGP standard, so participants might unknowingly know of a few people who use it already. If possible, make a list of people and organizations that use OpenPGP which participants will likely recognize by searching for <a href="https://duckduckgo.com/?q=%22BEGIN+PGP+PUBLIC+KEY+BLOCK%22+%2B+%22free+software%22">"BEGIN PGP PUBLIC KEY BLOCK" + keyword</a>.</p>
 122                                 </div><!-- End .section-intro -->
 123
 124                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 125                                 <div id="step-1a" class="step">
 126                                         <div class="sidebar">
 127                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png" alt="Step 2.A: Make a Keypair"></p>
 128                                         </div><!-- /.sidebar -->
 129                                         <div class="main">
 130                                                 <h3><em>Step 1.a</em> Space and Preparation</h3>
 131                                                 <p>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. Try and get all the participants to set up an Enigmail-compatible email client before the event. Direct them to their organizations IT department or help page if they run into errors. Estimate that the workshop to take at a minimum 30 minutes plus about five to 10 minutes for each participant. Plan extra time for glitches and questions.</p>
 132
 133                                         </div><!-- End .main -->
 134                                 </div><!-- End #terminology.step-->
 135
 136
 137                         </div>
 138                 </section><!-- End #section2 -->
 139
 140 <!-- ~~~~~~~~~ Section 2: Follow The Guide  ~~~~~~~~~ -->
 141                 <section class="row" id="section3">
 142                         <div>
 143                                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 144                                 <div class="section-intro">
 145                                                 <h2><em>#2</em> Follow The Guide</h2>
 146                                                 <p>Have the participants work through the Email Self-Defense guide a step at a time on their own computers. Make sure all participants complete each step before the group moves on to the next step. Talk about each step, but be sure not to overload the participants with minutia. Pitch the bulk of your instruction to the least tech-savvy participants. Consider holding a secondary workshop afterwards for the outliers in either direction.</p>
 147
 148                                 </div><!-- End .section-intro -->
 149
 150                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 151                                 <div id="step-2a" class="step">
 152                                         <div class="sidebar">
 153                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png" alt="Try it out."></p>
 154                                         </div><!-- /.sidebar -->
 155                                         <div class="main">
 156                                                 <h3><em>Step 2.a</em> Public and Private Keys key</h3>
 157                                                 <p>Make sure all the participants have a conceptual understanding of the relationship between public and private keys in a keypair. It's normal for people to not understand public-key cryptography on the first try. Use analogies to help explain the concept.</p>
 158
 159                                         </div><!-- End .main -->
 160                                 </div><!-- End #step-2a .step -->
 161
 162                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 163                                 <div id="step-2b" class="step">
 164 <div class="sidebar">
 165                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well" /></p>
 166                                                 </div><!-- /.sidebar -->
 167                                         <div class="main">
 168                                                         <h3><em>Step 2.b</em> Diceware and Passphrases</h3>
 169                                                         <p>Sufficiently strong passphrases <a href="https://firstlook.org/theintercept/2015/03/26/passphrases-can-memorize-attackers-cant-guess/"> can't easily be brute forced</a>, and thus protect the private key even if it falls into the wrong hands. Recommend participants use the <a href="http://world.std.com/~reinhold/diceware.html"> diceware method </a>, and have dice and the wordlist available for them to use. Participants who choose to use diceware should keep their passphrase with them at all at all times until they memorize it. Stress the importance of creating and backing up revocation certificates, especially to participants who write down their diceware passphrases.</p>
 170                                 <!-- ~~~~~~~~~ Troubleshooting  ~~~~~~~~~ -->
 171                                                 <div class="troubleshooting">
 172                                                         <h4>Disclaimer</h4>
 173                                                         <dl>
 174                                                                 <dt>Diceware and Licensing</dt>
 175                                                                         <dd>Something here about diceware's relationship with free software, or something.</dd>
 176                                                         </dl>
 177                                                 </div><!-- /.troubleshooting -->
 178
 179                                                 </div><!-- End .main -->
 180                                         </div><!-- End #step-3b .step -->
 181
 182
 183                         </div>
 184                 </section><!-- End #section3 -->
 185
 186
 187 <!-- ~~~~~~~~~ Section 3: Sign Keys  ~~~~~~~~~ -->
 188                 <section class="row" id="section4">
 189                         <div>
 190                                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 191                                 <div class="section-intro">
 192                                                 <h2><em>#3</em> Sign Keys</h2>
 193                                                 <p>Emphasize the distinction between trusting a person subjectively, and seeing whose keys they've signed objectively. Without a proper understanding of trust, the beautiful transative trust properties of the web of trust are lost. Since trust is an internal and subjective thing, it's unnecessary for participants to share how much they trust another participant with anyone else.</p>
 194
 195 <p>Have the participants download each other's keys, read out their own fingerprints, and present their IDs to each other. Help participants navigate the interface to sign each other's keys, and encourage participants to assign each other trust levels if they already know each other.</p>
 196
 197
 198
 199                                 </div><!-- End .section-intro -->
 200
 201                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 202                                 <div id="step-4a" class="step">
 203                                         <div class="sidebar">
 204                                                 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust"></p>
 205                                         </div><!-- /.sidebar -->
 206                                         <div class="main">
 207                                                 <h3><em>Step 4.a</em> Sign a key</h3>
 208                                                 <p>In your email program's menu, go to Enigmail → Key Management.</p>
 209                                                 <p>Right click on Edward's public key and select Sign Key from the context menu.</p>
 210                                                 <p>In the window that pops up, select "I will not answer" and click ok.</p>
 211                                                 <p>Now you should be back at the Key Management menu. Select Keyserver → Upload Public Keys and hit ok.</p>
 212                                                 <p class="notes">You've just effectively said "I trust that
 213 Edward's public key actually belongs to Edward." This doesn't mean much
 214 because Edward isn't a real person, but it's good practice.</p>
 215
 216
 217                                                 <!--<div id="pgp-pathfinder">
 218                                                         <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">
 219                                                                 <p><strong>From:</strong> <input type="text" placeholder="xD41A008"  name="FROM"></p>
 220                                                                 <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>
 221                                                                 <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>
 222                                                         </form>
 223                                                 </div><!-- End #pgp-pathfinder -->
 224
 225                                         </div><!-- End .main -->
 226                                 </div><!-- End #step-4a .step -->
 227
 228                                 <!-- ~~~~~~~~~ a div for each step  ~~~~~~~~~ -->
 229                                 <div id="step-sign_real_keys" class="step">
 230                                         <div class="main">
 231                                                 <h3><em>Important:</em> check people's identification before signing their keys</h3>
 232                                                 <p>Before signing a real person's key, always make sure it
 233 actually belongs to them, and that they are who they say they are. Ask
 234 them to show you their ID (unless you trust them very highly) and their
 235 public key fingerprint -- not just the shorter public key ID, which
 236 could refer to another key as well. In Enigmail, answer honestly in the
 237 window that pops up and asks "How carefully have you verified that the
 238 key you are about to sign actually belongs to the person(s) named
 239 above?".</p>
 240                                         </div><!-- End .main -->
 241                                 </div><!-- End #step-sign_real_keys .step-->
 242
 243
 244
 245                         </div>
 246                 </section><!-- End #section4 -->
 247
 248 <!-- ~~~~~~~~~ Section 4: Explain The Pitfalls  ~~~~~~~~~ -->
 249                 <section id="section5" class="row">
 250                         <div>
 251                                         <!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
 252                                 <div class="section-intro">
 253                                                 <h2><em>#4</em> Explain the pitfalls</h2>
 254 <p>Remind participants that encryption works only where it's explicitly used; they won't be able to send an encrypted email to someone who hasn't set up encrption already. Also remind them to make sure encryption is selected before hitting send. Explain metadata to the participants, and advise them to use bland-sounding subject lines.</p>
 255
 256 <p>Advocate for free software, for without it, we can't meaningfully resist invasions of our digital privacy and autonomy. Explain the  <a href="http://www.gnu.org/philosophy/proprietary-surveillance.html">dangers</a> of running a proprietary system, and why GnuPG can't begin to mitigate them.</p>
 257                                 </div><!-- End .section-intro -->
 258
 259
 260                         </div>
 261                 </section><!-- End #section5 -->
 262
 263
 264
 265 <!-- ~~~~~~~~~ Section 6: Next steps  ~~~~~~~~~ -->
 266                 <section class="row" id="section6">
 267                         <div id="step-click_here" class="step">
 268                                         <div class="main">
 269                                           <h2><a href="https://emailselfdefense.fsf.org/en/next_steps.html">Great job! Check out the next steps.</a></h2>
 270
 271                                         </div><!-- End .main -->
 272                                 </div><!-- End #step-click_here .step-->
 273
 274                 </section><!-- End #section6 -->
 275
 276 <!-- ~~~~~~~~~ FAQ  ~~~~~~~~~ -->
 277 <!-- When un-commenting this section go to main.css and search
 278                 for /* Guide Sections Background */ then add #faq to the desired color
 279
 280                 <section class="row" id="faq">
 281                         <div>
 282                                 <div class="sidebar">
 283                                         <h2>FAQ</h2>
 284                                 </div>
 285
 286                                 <div class="main">
 287                                         <dl>
 288                                                 <dt>My key expired</dt>
 289                                                         <dd>Answer coming soon.</dd>
 290
 291                                                 <dt>Who can read encrypted messages? Who can read signed ones?</dt>
 292                                                         <dd>Answer coming soon.</dd>
 293
 294                                                 <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>
 295                                                         <dd>Answer coming soon.</dd>
 296                                         </dl>
 297                                 </div>
 298                         </div>
 299                 </section> --><!-- End #faq -->
 300
 301 <!-- ~~~~~~~~~ Footer  ~~~~~~~~~ -->
 302                 <footer class="row" id="footer">
 303                         <div>
 304                                 <div id="copyright">
 305                                         <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>
 306                                         <p>Copyright &copy; 2014-2015 <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>
 307                                         <p><em><a href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">Source code of Edward reply bot by Josh Drake &lt;zamnedix@gnu.org&gt; available under the GNU General Public License.</a></em></p>
 308 <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>
 309                                         <p>Download the source package for <a href="emailselfdefense_source.zip">this guide</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>
 310                                         <p>
 311                                           <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
 312                                              rel="jslicense">
 313                                             JavaScript license information
 314                                           </a>
 315                                         </p>
 316                                 </div><!-- /#copyright -->
 317                                 <p class="credits">
 318                                         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>
 319                                 </p><!-- /.credits -->
 320                         </div>
 321                 </footer><!-- End #footer -->
 322
 323                 <script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
 324                 <script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
 325
 326                 <!-- Piwik -->
 327                 <script type="text/javascript">
 328                  /*
 329                  @licstart The following is the entire license notice for the
 330                     JavaScript code in this page.
 331
 332                  Copyright 2014 Matthieu Aubry
 333
 334                   This program is free software: you can redistribute it and/or modify
 335                  it under the terms of the GNU General Public License as published by
 336                  the Free Software Foundation, either version 3 of the License, or
 337                  (at your option) any later version.
 338
 339                   This program is distributed in the hope that it will be useful,
 340                  but WITHOUT ANY WARRANTY; without even the implied warranty of
 341                  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 342                  GNU General Public License for more details.
 343
 344                   You should have received a copy of the GNU General Public License
 345                  along with this program.  If not, see http://www.gnu.org/licenses/.
 346
 347                   @licend The above is the entire license notice
 348                      for the JavaScript code in this page.
 349                  */
 350                  var _paq = _paq || [];
 351                  _paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
 352                  _paq.push(["setCookieDomain", "*.www.fsf.org"]);
 353                  _paq.push(["setDomains", ["*.www.fsf.org","*.www.fsf.org"]]);
 354                  _paq.push(["trackPageView"]);
 355                  _paq.push(["enableLinkTracking"]);
 356
 357                  (function() {
 358                    var u=(("https:" == document.location.protocol) ? "https" : "http") + "://piwik.fsf.org/";
 359                    _paq.push(["setTrackerUrl", u+"piwik.php"]);
 360                    _paq.push(["setSiteId", "5"]);
 361                    var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
 362                    g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
 363                  })();
 364                 </script>
 365                 <!-- End Piwik Code -->
 366         </body>
 367 </html>