en/workshops.html

   1 <!DOCTYPE html>
   2 <html lang="en">
   3 <head>
   4 <meta http-equiv="content-type" content="text/html; charset=utf-8" />
   5 <title>Email Self-Defense - a guide to fighting surveillance with GnuPG
   6 encryption</title>
   7 <meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy,
   8 email, Enigmail" />
   9 <meta name="description" content="Email surveillance violates our fundamental
  10 rights and makes free speech risky. This guide will teach you email
  11 self-defense in 40 minutes with GnuPG." />
  12 <meta name="viewport" content="width=device-width, initial-scale=1" />
  13 <link rel="stylesheet" href="../static/css/main.css" />
  14 <link rel="shortcut icon"
  15 href="../static/img/favicon.ico" />
  16 </head>
  17
  18 <body>
  19 <div style="text-align: center; padding: 2.5px; background-color: #a94442; color:#fcf8e3;"><p>Due to Enigmail's PGP functionality being migrated into Icedove and Thunderbird, steps 2 and 3 of the guide are currently out of date.</p><p> Thank you for your patience while we're working on a new round of updates.</p></div>
  20
  21 <!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
  22 <header class="row" id="header"><div>
  23
  24 <h1>Email Self-Defense</h1>
  25
  26 <!-- Language list for browsers that do not have JS enabled -->
  27 <ul id="languages" class="os">
  28 <li><a class="current" href="/en">English - v5.0</a></li>
  29 <!--<li><a href="/cs">čeština - v4.0</a></li>
  30 <li><a href="/de">Deutsch - v4.0</a></li>
  31 <li><a href="/el">ελληνικά - v3.0</a></li>
  32 <li><a href="/es">español - v4.0</a></li>
  33 <li><a href="/fa">فارسی - v4.0</a></li>
  34 <li><a href="/fr">français - v4.0</a></li>
  35 <li><a href="/it">italiano - v3.0</a></li>
  36 <li><a href="/ja">日本語 - v4.0</a></li>
  37 <li><a href="/pt-br">português do Brasil - v3.0</a></li>
  38 <li><a href="/ro">română - v3.0</a></li>
  39 <li><a href="/ru">русский - v4.0</a></li>
  40 <li><a href="/sq">Shqip - v4.0</a></li>
  41 <li><a href="/sv">svenska - v4.0</a></li>
  42 <li><a href="/tr">Türkçe - v5.0</a></li>
  43 <li><a href="/zh-hans">简体中文 - v4.0</a></li>-->
  44 <li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide">
  45 <strong><span style="color: #2F5FAA;">Translate!</span></strong></a></li>
  46 </ul>
  47
  48 <ul id="menu" class="os">
  49 <li class="spacer"><a href="index.html">Set up guide</a></li>
  50 <!--<li><a href="mac.html">Mac OS</a></li>-->
  51 <!--<li><a href="windows.html">Windows</a></li>-->
  52 <li><a href="workshops.html" class="current">Teach your friends</a></li>
  53 <li><a href="https://fsf.org/share?u=https://u.fsf.org/zb&amp;t=Email%20encryption%20for%20everyone%20via%20%40fsf">Share&nbsp;
  54 <img
  55 src="../static/img/gnu-social.png" class="share-logo"
  56 alt="[GNU Social]" />&nbsp;
  57 <img
  58 src="../static/img/mastodon.png" class="share-logo"
  59 alt="[Mastodon]" />&nbsp;
  60 <img
  61 src="../static/img/reddit-alien.png" class="share-logo"
  62 alt="[Reddit]" />&nbsp;
  63 <img
  64 src="../static/img/hacker-news.png" class="share-logo"
  65 alt="[Hacker News]" />
  66 </a></li>
  67 </ul>
  68
  69 <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
  70 <div id="fsf-intro">
  71
  72 <h3><a href="https://u.fsf.org/ys"><img
  73 alt="Free Software Foundation"
  74 src="../static/img/fsf-logo.png" />
  75 </a></h3>
  76
  77 <div class="fsf-emphasis">
  78
  79 <p>We want to translate this guide
  80 into more languages, and make a version for encryption on mobile
  81 devices. Please donate, and help people around the world take the first
  82 step towards protecting their privacy with free software.</p>
  83
  84 </div>
  85
  86 <p><a
  87 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
  88 alt="Donate"
  89 src="../static/img/en/donate.png" /></a></p>
  90
  91 </div><!-- End #fsf-intro -->
  92
  93 <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
  94 <div class="intro">
  95
  96 <p><a id="infographic"
  97 href="infographic.html"><img
  98 src="../static/img/en/infographic-button.png"
  99 alt="View &amp; share our infographic →" /></a>
 100 Understanding and setting up email encryption sounds like a daunting task
 101 to many people. That's why helping your friends with GnuPG plays such an
 102 important role in helping spread encryption. Even if only one person shows
 103 up, that's still one more person using encryption who wasn't before. You have
 104 the power to help your friends keep their digital love letters private, and
 105 teach them about the importance of free software. If you use GnuPG to send and
 106 receive encrypted email, you're a perfect candidate for leading a workshop!</p>
 107
 108 </div><!-- End .intro -->
 109 </div></header><!-- End #header -->
 110
 111 <!-- ~~~~~~~~~ Section 1: Get your friends or community interested ~~~~~~~~~
 112 -->
 113 <section style="padding-top: 0px;" class="row" id="section1">
 114 <div style="padding-top: 0px;">
 115
 116 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
 117 <div class="section-intro">
 118 <p style="margin-top: 0px;" class="image"><img
 119 src="../static/img/en/screenshots/workshop-section1-update.png"
 120 alt="A small workshop among friends" /></p>
 121 <h2><em>#1</em> Get your friends or community interested </h2>
 122
 123 <p>If you hear friends grumbling about their lack of privacy, ask them if
 124 they're interested in attending a workshop on Email Self-Defense. If your
 125 friends don't grumble about privacy, they may need some convincing. You might
 126 even hear the classic "if you've got nothing to hide, you've got nothing to
 127 fear" argument against using encryption.</p>
 128
 129 <p>Here are some talking points you can use to help explain why it's worth
 130 it to learn GnuPG. Mix and match whichever you think will make sense to
 131 your community:</p>
 132
 133 </div><!-- End .section-intro -->
 134 <div id="step-aa" class="step">
 135 <div class="sidebar">
 136 <!-- Workshops image commented out from here, to be used above instead.
 137
 138 <p><img id="workshops-image"
 139 src="../static/img/en/screenshots/workshop-section1.png"
 140 alt="Workshop icon"></p>-->
 141 </div><!-- /.sidebar -->
 142 <div class="main">
 143
 144 <h3>Strength in numbers</h3>
 145
 146 <p>Each person who chooses to resist mass surveillance with encryption makes
 147 it easier for others to resist as well. People normalizing the use of strong
 148 encryption has multiple powerful effects: it means those who need privacy
 149 the most, like potential whistle-blowers and activists, are more likely to
 150 learn about encryption. More people using encryption for more things also
 151 makes it harder for surveillance systems to single out those that can't
 152 afford to be found, and shows solidarity with those people.</p>
 153
 154 </div><!-- End .main -->
 155 <div class="main">
 156
 157 <h3>People you respect may already be using encryption</h3>
 158
 159 <p>Many journalists, whistleblowers, activists, and researchers use GnuPG,
 160 so your friends might unknowingly have heard of a few people who use it
 161 already. You can search for "BEGIN PUBLIC KEY BLOCK" + keyword to help make
 162 a list of people and organizations who use GnuPG whom your community will
 163 likely recognize.</p>
 164
 165 </div><!-- End .main -->
 166 <div class="main">
 167
 168 <h3>Respect your friends' privacy</h3>
 169
 170 <p>There's no objective way to judge what constitutes privacy-sensitive
 171 correspondence. As such, it's better not to presume that just because you
 172 find an email you sent to a friend innocuous, your friend (or a surveillance
 173 agent, for that matter!) feels the same way. Show your friends respect by
 174 encrypting your correspondence with them.</p>
 175
 176 </div><!-- End .main -->
 177 <div class="main">
 178
 179 <h3>Privacy technology is normal in the physical world</h3>
 180
 181 <p>In the physical realm, we take window blinds, envelopes, and closed doors
 182 for granted as ways of protecting our privacy. Why should the digital realm
 183 be any different?</p>
 184
 185 </div><!-- End .main -->
 186 <div class="main">
 187
 188 <h3>We shouldn't have to trust our email providers with our privacy</h3>
 189
 190 <p>Some email providers are very trustworthy, but many have incentives not
 191 to protect your privacy and security. To be empowered digital citizens,
 192 we need to build our own security from the bottom up.</p>
 193
 194 </div><!-- End .main -->
 195 </div><!-- End #step-aa .step -->
 196 </div></section><!-- End #section1 -->
 197
 198 <!-- ~~~~~~~~~ Section 2: Plan The Workshop ~~~~~~~~~ -->
 199 <section class="row" id="section2"><div>
 200
 201 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
 202 <div class="section-intro" style="border: none; padding-bottom: 0px;
 203 margin-bottom: 0px;">
 204
 205 <h2><em>#2</em> Plan The Workshop</h2>
 206
 207 <p>Once you've got at least one interested friend, pick a date and start
 208 planning out the workshop. Tell participants to bring their computer and
 209 ID (for signing each other's keys). If you'd like to make it easy for the
 210 participants to use <a href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">Diceware</a> for choosing passwords, get a pack of dice
 211 beforehand. Make sure the location you select has an easily accessible
 212 Internet connection, and make backup plans in case the connection stops
 213 working on the day of the workshop. Libraries, coffee shops, and community
 214 centers make great locations. Try to get all the participants to set up
 215 an email client based on Thunderbird before the event. Direct them to their
 216 email provider's IT department or help page if they run into errors.</p>
 217
 218 <p>Estimate that the workshop will take at least forty minutes plus ten minutes
 219 for each participant. Plan extra time for questions and technical glitches.</p>
 220
 221 <p>The success of the workshop requires understanding and catering to
 222 the unique backgrounds and needs of each group of participants. Workshops
 223 should stay small, so that each participant receives more individualized
 224 instruction. If more than a handful of people want to participate, keep the
 225 facilitator to participant ratio high by recruiting more facilitators, or by
 226 facilitating multiple workshops. Small workshops among friends work great!</p>
 227
 228 </div><!-- End .section-intro -->
 229 </div></section><!-- End #section2 -->
 230
 231 <!-- ~~~~~~~~~ Section 3: Follow The Guide ~~~~~~~~~ -->
 232 <section class="row" id="section3"><div>
 233
 234 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
 235 <div class="section-intro" style="border: none; padding-bottom: 0px;
 236 margin-bottom: 0px;">
 237
 238 <h2><em>#3</em> Follow the guide as a group</h2>
 239
 240 <p>Work through the Email Self-Defense guide a step at a time as a group. Talk
 241 about the steps in detail, but make sure not to overload the participants
 242 with minutia. Pitch the bulk of your instructions to the least tech-savvy
 243 participants. Make sure all the participants complete each step before the
 244 group moves on to the next one. Consider facilitating secondary workshops
 245 afterwards for people that had trouble grasping the concepts, or those that
 246 grasped them quickly and want to learn more.</p>
 247
 248 <p>In <a href="index.html#section2">Section 2</a> of the guide, make
 249 sure the participants upload their keys to the same keyserver so that
 250 they can immediately download each other's keys later (sometimes
 251 there is a delay in synchronization between keyservers). During <a
 252 href="index.html#section3">Section 3</a>, give the participants the option to
 253 send test messages to each other instead of or as well as Edward. Similarly,
 254 in <a href="index.html#section4">Section 4</a>, encourage the participants
 255 to sign each other's keys. At the end, make sure to remind people to safely
 256 back up their revocation certificates.</p>
 257
 258 </div><!-- End .section-intro -->
 259 </div></section>
 260
 261 <!-- ~~~~~~~~~ Section 4: Explain the pitfalls ~~~~~~~~~ -->
 262 <section class="row" id="section4"><div>
 263
 264 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
 265 <div class="section-intro" style="border: none; padding-bottom: 0px;
 266 margin-bottom: 0px;">
 267
 268 <h2><em>#4</em> Explain the pitfalls</h2>
 269
 270 <p>Remind participants that encryption works only when it's explicitly used;
 271 they won't be able to send an encrypted email to someone who hasn't already
 272 set up encryption. Also remind participants to double-check the encryption icon
 273 before hitting send, and that subjects and timestamps are never encrypted.</p>
 274
 275 <p> Explain the <a
 276 href="https://www.gnu.org/proprietary/proprietary.html">dangers
 277 of running a proprietary system</a> and
 278 advocate for free software, because without it, we can't <a
 279 href="https://www.fsf.org/bulletin/2013/fall/how-can-free-software-protect-us-from-surveillance">meaningfully
 280 resist invasions of our digital privacy and autonomy</a>.</p>
 281
 282 </div><!-- End .section-intro -->
 283 </div></section><!-- End #section4 -->
 284
 285 <!-- ~~~~~~~~~ Section 5: Explain The Pitfalls ~~~~~~~~~ -->
 286 <section id="section5" class="row"><div>
 287
 288 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
 289 <div class="section-intro" style="border: none; padding-bottom: 0px;
 290 margin-bottom: 0px;">
 291
 292 <h2><em>#5</em> Share additional resources</h2>
 293
 294 <p>GnuPG's advanced options are far too complex to teach in a single
 295 workshop. If participants want to know more, point out the advanced subsections
 296 in the guide and consider organizing another workshop. You can also share
 297 <a href="https://www.gnupg.org/documentation/index.html">GnuPG's</a>
 298 official documentation and mailing lists, and the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Email Self-Defense feedback</a> page. Many GNU/Linux distribution's Web
 299 sites also contain a page explaining some of GnuPG's advanced features.</p>
 300
 301 </div><!-- End .section-intro -->
 302 </div></section><!-- End #section5 -->
 303
 304 <!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
 305 <section class="row" id="section6"><div>
 306
 307 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
 308 <div class="section-intro" style="border: none; padding-bottom: 0px;
 309 margin-bottom: 0px;">
 310
 311 <h2><em>#6</em> Follow up</h2>
 312
 313 <p>Make sure everyone has shared email addresses and public key fingerprints
 314 before they leave. Encourage the participants to continue to gain GnuPG
 315 experience by emailing each other. Send them each an encrypted email one
 316 week after the event, reminding them to try adding their public key ID to
 317 places where they publicly list their email address.</p>
 318
 319 <p>If you have any suggestions for improving this workshop guide, please
 320 let us know at <a href="mailto:campaigns@fsf.org">campaigns@fsf.org</a>.</p>
 321
 322 </div><!-- End .section-intro -->
 323 </div></section><!-- End #section6 -->
 324 <!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
 325 <footer class="row" id="footer"><div>
 326 <div id="copyright">
 327
 328 <h4><a href="https://u.fsf.org/ys"><img
 329 alt="Free Software Foundation"
 330 src="../static/img/fsf-logo.png" /></a></h4>
 331
 332 <p>Copyright &copy; 2014-2021 <a
 333 href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a
 334 href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please
 335 support our work by <a href="https://u.fsf.org/yr">joining us as an associate
 336 member.</a></p>
 337
 338 <p>The images on this page are under a <a
 339 href="https://creativecommons.org/licenses/by/4.0/">Creative Commons
 340 Attribution 4.0 license (or later version)</a>, and the rest of it is under
 341 a <a href="https://creativecommons.org/licenses/by-sa/4.0">Creative Commons
 342 Attribution-ShareAlike 4.0 license (or later version)</a>. Download the <a
 343 href="https://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">
 344 source code of Edward reply bot</a> by Andrew Engelbrecht
 345 &lt;andrew@engelbrecht.io&gt; and Josh Drake &lt;zamnedix@gnu.org&gt;,
 346 available under the GNU Affero General Public License. <a
 347 href="https://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these
 348 licenses?</a></p>
 349
 350 <p>Fonts used in the guide &amp; infographic: <a
 351 href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> by Pablo
 352 Impallari, <a href="https://www.google.com/fonts/specimen/Signika">Signika</a>
 353 by Anna Giedry&#347;, <a
 354 href="https://www.google.com/fonts/specimen/Archivo+Narrow">Archivo
 355 Narrow</a> by Omnibus-Type, <a
 356 href="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a>
 357 by Florian Cramer.</p>
 358
 359 <p>Download the <a href="emailselfdefense_source.zip">source package</a>
 360 for this guide, including fonts, image source files and the text of Edward's
 361 messages.</p>
 362
 363 <p>This site uses the Weblabels standard for labeling <a
 364 href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View
 365 the JavaScript <a href="https://weblabels.fsf.org/emailselfdefense.fsf.org/"
 366 rel="jslicense">source code and license information</a>.</p>
 367
 368 </div><!-- /#copyright -->
 369
 370 <p class="credits">Infographic and guide design by <a rel="external"
 371 href="https://jplusplus.org"><strong>Journalism++</strong><img
 372 src="../static/img/jplusplus.png"
 373 alt="Journalism++" /></a></p><!-- /.credits -->
 374 </div></footer><!-- End #footer -->
 375
 376 <script type="text/javascript"
 377 src="../static/js/jquery-1.11.0.min.js"></script>
 378 <script type="text/javascript"
 379 src="../static/js/scripts.js"></script>
 380 <!-- Piwik -->
 381 <script type="text/javascript">
 382   // @license magnet:?xt=urn:btih:cf05388f2679ee054f2beb29a391d25f4e673ac3&dn=gpl-2.0.txt GPL-2.0-or-later
 383   var _paq = _paq || [];
 384   _paq.push(["trackPageView"]);
 385   _paq.push(["enableLinkTracking"]);
 386
 387   (function() {
 388     var u = (("https:" == document.location.protocol) ? "https" : "http") + "://"+"piwik.fsf.org//";
 389     _paq.push(["setTrackerUrl", u+"piwik.php"]);
 390     _paq.push(["setSiteId", "13"]);
 391     var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
 392     g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
 393   })();
 394   // @license-end
 395 </script>
 396 <!-- End Piwik Code -->
 397 <!-- Piwik Image Tracker -->
 398 <noscript><img src="https://piwik.fsf.org//piwik.php?idsite=13&amp;rec=1" style="border:0" alt="" /></noscript>
 399 <!-- End Piwik -->
 400 </body>
 401 </html>