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