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