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