Merge branch 'master' of vcs.fsf.org:enc
[enc.git] / 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 <!-- Language list for browsers that do not have JS enabled -->
24 <ul id="languages" class="os">
25 <li><a class="current" href="/en">english</a></li>
26 <li><a 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="/it">italiano</a></li>
30 <li><a href="/pt-br">português do Brasil</a></li>
31 <li><a href="/tr">türkçe</a></li>
32 <li><a href="/ro">română</a></li>
33 <li><a href="/ru">русский</a></li>
34 <!--<li><a href="/ml">മലയാളം</a></li>-->
35 <!--<li><a href="/ko">한국어</a></li>-->
36 <li><a href="/ja">日本語</a></li>
37 <li><a href="/el">ελληνικά</a></li>
38 <!--<li><a href="/ar">العربية</a></li>-->
39 </ul>
40
41 <ul id="menu" class="os">
42 <li class="spacer">
43 <a href="index.html">GNU/Linux</a>
44 </li>
45 <li>
46 <a href="mac.html">Mac OS</a>
47 </li>
48 <li>
49 <a href="windows.html">Windows</a>
50 </li>
51 <li class="spacer"><a href="workshops.html" class="current">Lead a Workshop</a></li>
52 <li class="spacer">
53 <a href="https://fsf.org/share?u=https://u.fsf.org/zb&amp;t=Email encryption for everyone via %40fsf">
54 Share&nbsp;
55 <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png"
56 class="share-logo" alt="[GNU Social]">&nbsp;
57 <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png"
58 class="share-logo" alt="[Pump.io]">&nbsp;
59 <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png"
60 class="share-logo" alt="[Reddit]">&nbsp;
61 <img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png"
62 class="share-logo" alt="[Hacker News]">
63 </a>
64 </li>
65 <li class="spacer">V4.0</li>
66 </ul>
67 <!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
68 <div id="fsf-intro">
69 <h3>
70 <a href="http://u.fsf.org/ys">
71 <img alt="Free Software Foundation" src="https://static.fsf.org/nosvn/enc-dev0/img/en/fsf-logo.png">
72 </a>
73 </h3>
74 <div class="fsf-emphasis">
75 <p>
76 We fight for computer users'
77 rights, and promote the development of free (as in freedom) software.
78 Resisting bulk surveillance is very important to us.
79 </p>
80 <p>
81 <strong>
82 We want to translate this guide
83 into more languages, and make a version for encryption on mobile
84 devices. Please donate, and help people around the world take the first
85 step towards protecting their privacy with free software.
86 </strong>
87 </p>
88 </div>
89
90 <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="https://static.fsf.org/nosvn/enc-dev0/img/en/donate.png"></a> </p>
91
92 </div><!-- End #fsf-intro -->
93
94 <!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
95 <div class="intro">
96 <p>
97 <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>
98 <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>
99
100 </div><!-- End .intro -->
101
102 </div>
103 </header><!-- End #header -->
104
105 <!-- ~~~~~~~~~ Section 1: Get your friends or community interested> ~~~~~~~~~ -->
106 <section class="row" id="section1">
107 <div>
108 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
109 <div class="section-intro">
110 <h2><em>#1</em> Get your friends or community interested </h2>
111 <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>
112 <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>
113
114 </div><!-- End .section-intro -->
115 </div>
116 </section><!-- End #section0 -->
117
118 <!-- ~~~~~~~~~ Section 1: Plan The Workshop ~~~~~~~~~ -->
119 <section class="row" id="section2">
120 <div>
121 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
122 <div class="section-intro">
123 <h2><em>#1</em> Plan The Workshop</h2>
124 <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>
125
126 <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>
127
128 <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>
129 </div><!-- End .section-intro -->
130
131 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
132 <div id="step-1a" class="step">
133 <div class="sidebar">
134 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png" alt="Step 2.A: Make a Keypair"></p>
135 </div><!-- /.sidebar -->
136 <div class="main">
137 <h3><em>Step 1.a</em> Space and Preparation</h3>
138 <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>
139
140 </div><!-- End .main -->
141 </div><!-- End #terminology.step-->
142
143
144 </div>
145 </section><!-- End #section2 -->
146
147 <!-- ~~~~~~~~~ Section 2: Follow The Guide ~~~~~~~~~ -->
148 <section class="row" id="section3">
149 <div>
150 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
151 <div class="section-intro">
152 <h2><em>#2</em> Follow The Guide</h2>
153 <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>
154
155 </div><!-- End .section-intro -->
156
157 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
158 <div id="step-2a" class="step">
159 <div class="sidebar">
160 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png" alt="Try it out."></p>
161 </div><!-- /.sidebar -->
162 <div class="main">
163 <h3><em>Step 2.a</em> Public and Private Keys key</h3>
164 <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>
165
166 </div><!-- End .main -->
167 </div><!-- End #step-2a .step -->
168
169 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
170 <div id="step-2b" class="step">
171 <div class="sidebar">
172 <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>
173 </div><!-- /.sidebar -->
174 <div class="main">
175 <h3><em>Step 2.b</em> Diceware and Passphrases</h3>
176 <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>
177 <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
178 <div class="troubleshooting">
179 <h4>Disclaimer</h4>
180 <dl>
181 <dt>Diceware and Licensing</dt>
182 <dd>Something here about diceware's relationship with free software, or something.</dd>
183 </dl>
184 </div><!-- /.troubleshooting -->
185
186 </div><!-- End .main -->
187 </div><!-- End #step-3b .step -->
188
189
190 </div>
191 </section><!-- End #section3 -->
192
193
194 <!-- ~~~~~~~~~ Section 3: Sign Keys ~~~~~~~~~ -->
195 <section class="row" id="section4">
196 <div>
197 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
198 <div class="section-intro">
199 <h2><em>#3</em> Sign Keys</h2>
200 <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>
201
202 <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>
203
204
205
206 </div><!-- End .section-intro -->
207
208 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
209 <div id="step-4a" class="step">
210 <div class="sidebar">
211 <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust"></p>
212 </div><!-- /.sidebar -->
213 <div class="main">
214 <h3><em>Step 4.a</em> Sign a key</h3>
215 <p>In your email program's menu, go to Enigmail → Key Management.</p>
216 <p>Right click on Edward's public key and select Sign Key from the context menu.</p>
217 <p>In the window that pops up, select "I will not answer" and click ok.</p>
218 <p>Now you should be back at the Key Management menu. Select Keyserver → Upload Public Keys and hit ok.</p>
219 <p class="notes">You've just effectively said "I trust that
220 Edward's public key actually belongs to Edward." This doesn't mean much
221 because Edward isn't a real person, but it's good practice.</p>
222
223
224 <!--<div id="pgp-pathfinder">
225 <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">
226 <p><strong>From:</strong> <input type="text" placeholder="xD41A008" name="FROM"></p>
227 <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>
228 <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>
229 </form>
230 </div><!-- End #pgp-pathfinder -->
231
232 </div><!-- End .main -->
233 </div><!-- End #step-4a .step -->
234
235 <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
236 <div id="step-sign_real_keys" class="step">
237 <div class="main">
238 <h3><em>Important:</em> check people's identification before signing their keys</h3>
239 <p>Before signing a real person's key, always make sure it
240 actually belongs to them, and that they are who they say they are. Ask
241 them to show you their ID (unless you trust them very highly) and their
242 public key fingerprint -- not just the shorter public key ID, which
243 could refer to another key as well. In Enigmail, answer honestly in the
244 window that pops up and asks "How carefully have you verified that the
245 key you are about to sign actually belongs to the person(s) named
246 above?".</p>
247 </div><!-- End .main -->
248 </div><!-- End #step-sign_real_keys .step-->
249
250
251
252 </div>
253 </section><!-- End #section4 -->
254
255 <!-- ~~~~~~~~~ Section 4: Explain The Pitfalls ~~~~~~~~~ -->
256 <section id="section5" class="row">
257 <div>
258 <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
259 <div class="section-intro">
260 <h2><em>#4</em> Explain the pitfalls</h2>
261 <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>
262
263 <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>
264 </div><!-- End .section-intro -->
265
266
267 </div>
268 </section><!-- End #section5 -->
269
270
271
272 <!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
273 <section class="row" id="section6">
274 <div id="step-click_here" class="step">
275 <div class="main">
276 <h2><a href="https://emailselfdefense.fsf.org/en/next_steps.html">Great job! Check out the next steps.</a></h2>
277
278 </div><!-- End .main -->
279 </div><!-- End #step-click_here .step-->
280
281 </section><!-- End #section6 -->
282
283 <!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
284 <!-- When un-commenting this section go to main.css and search
285 for /* Guide Sections Background */ then add #faq to the desired color
286
287 <section class="row" id="faq">
288 <div>
289 <div class="sidebar">
290 <h2>FAQ</h2>
291 </div>
292
293 <div class="main">
294 <dl>
295 <dt>My key expired</dt>
296 <dd>Answer coming soon.</dd>
297
298 <dt>Who can read encrypted messages? Who can read signed ones?</dt>
299 <dd>Answer coming soon.</dd>
300
301 <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>
302 <dd>Answer coming soon.</dd>
303 </dl>
304 </div>
305 </div>
306 </section> --><!-- End #faq -->
307
308 <!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
309 <footer class="row" id="footer">
310 <div>
311 <div id="copyright">
312 <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>
313 <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>
314 <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>
315 <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>
316 <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>
317 <p>
318 <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
319 rel="jslicense">
320 JavaScript license information
321 </a>
322 </p>
323 </div><!-- /#copyright -->
324 <p class="credits">
325 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>
326 </p><!-- /.credits -->
327 </div>
328 </footer><!-- End #footer -->
329
330 <script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
331 <script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
332
333 <!-- Piwik -->
334 <script type="text/javascript">
335 /*
336 @licstart The following is the entire license notice for the
337 JavaScript code in this page.
338
339 Copyright 2014 Matthieu Aubry
340
341 This program is free software: you can redistribute it and/or modify
342 it under the terms of the GNU General Public License as published by
343 the Free Software Foundation, either version 3 of the License, or
344 (at your option) any later version.
345
346 This program is distributed in the hope that it will be useful,
347 but WITHOUT ANY WARRANTY; without even the implied warranty of
348 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
349 GNU General Public License for more details.
350
351 You should have received a copy of the GNU General Public License
352 along with this program. If not, see http://www.gnu.org/licenses/.
353
354 @licend The above is the entire license notice
355 for the JavaScript code in this page.
356 */
357 var _paq = _paq || [];
358 _paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
359 _paq.push(["setCookieDomain", "*.www.fsf.org"]);
360 _paq.push(["setDomains", ["*.www.fsf.org","*.www.fsf.org"]]);
361 _paq.push(["trackPageView"]);
362 _paq.push(["enableLinkTracking"]);
363
364 (function() {
365 var u=(("https:" == document.location.protocol) ? "https" : "http") + "://piwik.fsf.org/";
366 _paq.push(["setTrackerUrl", u+"piwik.php"]);
367 _paq.push(["setSiteId", "5"]);
368 var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
369 g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
370 })();
371 </script>
372 <!-- End Piwik Code -->
373 </body>
374 </html>