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