[enc-live.git] / en / workshops.html

<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>Email Self-Defense - a guide to fighting surveillance with GnuPG
encryption</title>
<meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy,
email, Enigmail" />
<meta name="description" content="Email surveillance violates our fundamental
rights and makes free speech risky. This guide will teach you email
self-defense in 40 minutes with GnuPG." />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css" />
<link rel="shortcut icon"
href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />
</head>

<body>

<!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
<header class="row" id="header"><div>

<h1>Email Self-Defense</h1>

<!-- Language list for browsers that do not have JS enabled -->
<ul id="languages" class="os">
<li><a class="current" href="/en">English - v4.0</a></li>
<li><a href="/cs">čeština - v4.0</a></li>
<li><a href="/de">Deutsch - v4.0</a></li>
<li><a href="/el">ελληνικά - v3.0</a></li>
<li><a href="/es">español - v4.0</a></li>
<li><a href="/fa">فارسی - v4.0</a></li>
<li><a href="/fr">français - v4.0</a></li>
<li><a href="/it">italiano - v3.0</a></li>
<li><a href="/ja">日本語 - v4.0</a></li>
<li><a href="/pt-br">português do Brasil - v3.0</a></li>
<li><a href="/ro">română - v3.0</a></li>
<li><a href="/ru">русский - v4.0</a></li>
<li><a href="/sq">Shqip - v4.0</a></li>
<li><a href="/sv">svenska - v4.0</a></li>
<li><a href="/tr">Türkçe - v4.0</a></li>
<li><a href="/zh-hans">简体中文 - v4.0</a></li>
<li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide">
<strong><span style="color: #2F5FAA;">Translate!</span></strong></a></li>
</ul>

<ul id="menu" class="os">
<li class="spacer"><a href="index.html">GNU/Linux</a></li>
<li><a href="mac.html">Mac OS</a></li>
<li><a href="windows.html">Windows</a></li>
<li><a href="workshops.html" class="current">Teach your friends</a></li>
<li><a href="https://fsf.org/share?u=https://u.fsf.org/zb&amp;t=Email
encryption for everyone via %40fsf">Share&nbsp;
<img
src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png" class="share-logo"
alt="[GNU Social]" />&nbsp;
<img
src="//static.fsf.org/nosvn/enc-dev0/img/mastodon.png" class="share-logo"
alt="[Mastodon]" />&nbsp;
<img
src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png" class="share-logo"
alt="[Reddit]" />&nbsp;
<img
src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png" class="share-logo"
alt="[Hacker News]" />
</a></li>
</ul>

<!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
<div id="fsf-intro">

<h3><a href="http://u.fsf.org/ys"><img
alt="Free Software Foundation"
src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" />
</a></h3>

<div class="fsf-emphasis">

<p>We want to translate this guide
into more languages, and make a version for encryption on mobile
devices. Please donate, and help people around the world take the first
step towards protecting their privacy with free software.</p>

</div>

<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="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png" /></a></p>

</div><!-- End #fsf-intro -->

<!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
<div class="intro">

<p><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>
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>

</div><!-- End .intro -->
</div></header><!-- End #header -->

<!-- ~~~~~~~~~ Section 1: Get your friends or community interested ~~~~~~~~~
-->
<section style="padding-top: 0px;" class="row" id="section1">
<div style="padding-top: 0px;">

<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro">

<p style="margin-top: 0px;" class="image"><img
src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/workshop-section1.png"
alt="A small workshop among friends" /></p>

<h2><em>#1</em> Get your friends or community interested </h2>

<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>

<p>Here are some talking points you can use to help explain why it's worth
it to learn GnuPG. Mix and match whichever you think will make sense to
your community:</p>

</div><!-- End .section-intro -->
<div id="step-aa" class="step">
<div class="sidebar">
<!-- Workshops image commented out from here, to be used above instead.

<p><img id="workshops-image"
src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/workshop-section1.png"
alt="Workshop icon"></p>-->
</div><!-- /.sidebar -->
<div class="main">

<h3>Strength in numbers</h3>

<p>Each person who chooses to resist mass surveillance with encryption makes
it easier for others to resist as well. People normalizing the use of strong
encryption has multiple powerful effects: it means those who need privacy
the most, like potential whistle-blowers and activists, are more likely to
learn about encryption. More people using encryption for more things also
makes it harder for surveillance systems to single out those that can't
afford to be found, and shows solidarity with those people.</p>

</div><!-- End .main -->
<div class="main">

<h3>People you respect may already be using encryption</h3>

<p>Many journalists, whistleblowers, activists, and researchers use GnuPG,
so your friends might unknowingly have heard of a few people who use it
already. You can search for "BEGIN PUBLIC KEY BLOCK" + keyword to help make
a list of people and organizations who use GnuPG whom your community will
likely recognize.</p>

</div><!-- End .main -->
<div class="main">

<h3>Respect your friends' privacy</h3>

<p>There's no objective way to judge what constitutes privacy-sensitive
correspondence. As such, it's better not to presume that just because you
find an email you sent to a friend innocuous, your friend (or a surveillance
agent, for that matter!) feels the same way. Show your friends respect by
encrypting your correspondence with them.</p>

</div><!-- End .main -->
<div class="main">

<h3>Privacy technology is normal in the physical world</h3>

<p>In the physical realm, we take window blinds, envelopes, and closed doors
for granted as ways of protecting our privacy. Why should the digital realm
be any different?</p>

</div><!-- End .main -->
<div class="main">

<h3>We shouldn't have to trust our email providers with our privacy</h3>

<p>Some email providers are very trustworthy, but many have incentives not
to protect your privacy and security. To be empowered digital citizens,
we need to build our own security from the bottom up.</p>

</div><!-- End .main -->
</div><!-- End #step-aa .step -->
</div></section><!-- End #section1 -->

<!-- ~~~~~~~~~ Section 2: Plan The Workshop ~~~~~~~~~ -->
<section class="row" id="section2"><div>

<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro" style="border: none; padding-bottom: 0px;
margin-bottom: 0px;">

<h2><em>#2</em> Plan The Workshop</h2>

<p>Once you've got at least one interested friend, pick a date and start
planning out the workshop. Tell participants to bring their computer and
ID (for signing each other's keys). If you'd like to make it easy for the
participants to use Diceware for choosing passwords, get a pack of dice
beforehand. 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. Libraries, coffee shops, and community
centers make great locations. Try to get all the participants to set up
an Enigmail-compatible email client before the event. Direct them to their
email provider's IT department or help page if they run into errors.</p>

<p>Estimate that the workshop will take at least forty minutes plus ten minutes
for each participant. Plan extra time for questions and technical glitches.</p>

<p>The success of the workshop requires understanding and catering to
the unique backgrounds and needs of each group of participants. Workshops
should stay small, so that each participant receives more individualized
instruction. If more than a handful of people want to participate, keep the
facilitator to participant ratio high by recruiting more facilitators, or by
facilitating multiple workshops. Small workshops among friends work great!</p>

</div><!-- End .section-intro -->
</div></section><!-- End #section2 -->

<!-- ~~~~~~~~~ Section 3: Follow The Guide ~~~~~~~~~ -->
<section class="row" id="section3"><div>

<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro" style="border: none; padding-bottom: 0px;
margin-bottom: 0px;">

<h2><em>#3</em> Follow the guide as a group</h2>

<p>Work through the Email Self-Defense guide a step at a time as a group. Talk
about the steps in detail, but make sure not to overload the participants
with minutia. Pitch the bulk of your instructions to the least tech-savvy
participants. Make sure all the participants complete each step before the
group moves on to the next one. Consider facilitating secondary workshops
afterwards for people that had trouble grasping the concepts, or those that
grasped them quickly and want to learn more.</p>

<p>In <a href="index.html#section2">Section 2</a> of the guide, make
sure the participants upload their keys to the same keyserver so that
they can immediately download each other's keys later (sometimes
there is a delay in synchronization between keyservers). During <a
href="index.html#section3">Section 3</a>, give the participants the option to
send test messages to each other instead of or as well as Edward. Similarly,
in <a href="index.html#section4">Section 4</a>, encourage the participants
to sign each other's keys. At the end, make sure to remind people to safely
back up their revocation certificates.</p>

</div><!-- End .section-intro -->
</div></section>

<!-- ~~~~~~~~~ Section 4: Explain the pitfalls ~~~~~~~~~ -->
<section class="row" id="section4"><div>

<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro" style="border: none; padding-bottom: 0px;
margin-bottom: 0px;">

<h2><em>#4</em> Explain the pitfalls</h2>

<p>Remind participants that encryption works only when it's explicitly used;
they won't be able to send an encrypted email to someone who hasn't already
set up encryption. Also remind participants to double-check the encryption icon
before hitting send, and that subjects and timestamps are never encrypted.</p>

<p> Explain the <a
href="https://www.gnu.org/proprietary/proprietary.html">dangers
of running a proprietary system</a> and
advocate for free software, because without it, we can't <a
href="https://www.fsf.org/bulletin/2013/fall/how-can-free-software-protect-us-from-surveillance">meaningfully
resist invasions of our digital privacy and autonomy</a>.</p>

</div><!-- End .section-intro -->
</div></section><!-- End #section4 -->

<!-- ~~~~~~~~~ Section 5: Explain The Pitfalls ~~~~~~~~~ -->
<section id="section5" class="row"><div>

<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro" style="border: none; padding-bottom: 0px;
margin-bottom: 0px;">

<h2><em>#5</em> Share additional resources</h2>

<p>GnuPG's advanced options are far too complex to teach in a single
workshop. If participants want to know more, point out the advanced subsections
in the guide and consider organizing another workshop. You can also share
<a href="https://www.gnupg.org/documentation/index.html">GnuPG's</a> and
<a href="https://www.enigmail.net/index.php/documentation">Enigmail's</a>
official documentation and mailing lists. Many GNU/Linux distribution's Web
sites also contain a page explaining some of GnuPG's advanced features.</p>

</div><!-- End .section-intro -->
</div></section><!-- End #section5 -->

<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
<section class="row" id="section6"><div>

<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
<div class="section-intro" style="border: none; padding-bottom: 0px;
margin-bottom: 0px;">

<h2><em>#6</em> Follow up</h2>

<p>Make sure everyone has shared email addresses and public key fingerprints
before they leave. Encourage the participants to continue to gain GnuPG
experience by emailing each other. Send them each an encrypted email one
week after the event, reminding them to try adding their public key ID to
places where they publicly list their email address.</p>

<p>If you have any suggestions for improving this workshop guide, please
let us know at <a href="mailto:campaigns@fsf.org">campaigns@fsf.org</a>.</p>

</div><!-- End .section-intro -->
</div></section><!-- End #section6 -->
<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
<footer class="row" id="footer"><div>
<div id="copyright">

<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>

<p>Copyright &copy; 2014-2016 <a
href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a
href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please
support our work by <a href="https://u.fsf.org/yr">joining us as an associate
member.</a></p>

<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>. Download the <a
href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">
source code of Edward reply bot</a> by Andrew Engelbrecht
&lt;sudoman@ninthfloor.org&gt; and Josh Drake &lt;zamnedix@gnu.org&gt;,
available under the GNU Affero General Public License. <a
href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these
licenses?</a></p>

<p>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="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a>
by Florian Cramer.</p>

<p>Download the <a href="emailselfdefense_source.zip">source package</a>
for this guide, including fonts, image source files and the text of Edward's
messages.</p>

<p>This site uses the Weblabels standard for labeling <a
href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View
the JavaScript <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
rel="jslicense">source code and license information</a>.</p>

</div><!-- /#copyright -->

<p class="credits">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></p><!-- /.credits -->
</div></footer><!-- End #footer -->

<script type="text/javascript"
src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
<script type="text/javascript"
src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
<!-- Piwik -->
<script type="text/javascript">
  // @license magnet:?xt=urn:btih:cf05388f2679ee054f2beb29a391d25f4e673ac3&dn=gpl-2.0.txt GPL-2.0-or-later
  var _paq = _paq || [];
  _paq.push(["trackPageView"]);
  _paq.push(["enableLinkTracking"]);

  (function() {
    var u = (("https:" == document.location.protocol) ? "https" : "http") + "://"+"piwik.fsf.org//";
    _paq.push(["setTrackerUrl", u+"piwik.php"]);
    _paq.push(["setSiteId", "13"]);
    var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
    g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
  })();
  // @license-end
</script>
<!-- End Piwik Code -->
<!-- Piwik Image Tracker -->
<noscript><img src="https://piwik.fsf.org//piwik.php?idsite=13&rec=1" style="border:0" alt="" /></noscript>
<!-- End Piwik -->
</body>
</html>
Commit	Line	Data
19bce4d7 TG	1	<!DOCTYPE html>
	2	<html lang="en">
	3	<head>
	4	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
d06ce723 TG	5	<title>Email Self-Defense - a guide to fighting surveillance with GnuPG
d06ce723 TG	6	encryption</title>
19bce4d7 TG	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" />
2c595172	16	</head>
19bce4d7	17
f12cd56f	18	<body>
2c595172	19
19bce4d7 TG	20	<!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
19bce4d7 TG	21	<header class="row" id="header"><div>
2c595172	22
19bce4d7	23	<h1>Email Self-Defense</h1>
2c595172	24
19bce4d7 TG	25	<!-- Language list for browsers that do not have JS enabled -->
19bce4d7 TG	26	<ul id="languages" class="os">
7c4f505e	27	<li><a class="current" href="/en">English - v4.0</a></li>
c1fa777e	28	<li><a href="/cs">čeština - v4.0</a></li>
f7d7ddc2	29	<li><a href="/de">Deutsch - v4.0</a></li>
7c4f505e ZR	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>
7c4f505e ZR	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>
19bce4d7	39	<li><a href="/sq">Shqip - v4.0</a></li>
7c4f505e ZR	40	<li><a href="/sv">svenska - v4.0</a></li>
7c4f505e ZR	41	<li><a href="/tr">Türkçe - v4.0</a></li>
597f7b15	42	<li><a href="/zh-hans">简体中文 - v4.0</a></li>
ce9d37a4 TG	43	<li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide">
ce9d37a4 TG	44	<strong><span style="color: #2F5FAA;">Translate!</span></strong></a></li>
19bce4d7 TG	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&t=Email
	53	encryption for everyone via %40fsf">Share
	54	<img
	55	src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png" class="share-logo"
	56	alt="[GNU Social]" />
	57	<img
d06ce723 TG	58	src="//static.fsf.org/nosvn/enc-dev0/img/mastodon.png" class="share-logo"
d06ce723 TG	59	alt="[Mastodon]" />
19bce4d7 TG	60	<img
	61	src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png" class="share-logo"
	62	alt="[Reddit]" />
	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>
2c595172	83
19bce4d7	84	</div>
2c595172	85
19bce4d7 TG	86	<p><a
	87	href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&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 & 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.
2c595172	139
19bce4d7 TG	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">
2c595172	145
19bce4d7	146	<h3>Strength in numbers</h3>
2c595172	147
19bce4d7 TG	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">
2c595172	158
19bce4d7	159	<h3>People you respect may already be using encryption</h3>
d083698e	160
19bce4d7 TG	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>
2c595172	166
19bce4d7 TG	167	</div><!-- End .main -->
19bce4d7 TG	168	<div class="main">
2c595172	169
19bce4d7	170	<h3>Respect your friends' privacy</h3>
2c595172	171
19bce4d7 TG	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>
2c595172	177
19bce4d7 TG	178	</div><!-- End .main -->
19bce4d7 TG	179	<div class="main">
2c595172	180
19bce4d7	181	<h3>Privacy technology is normal in the physical world</h3>
2c595172	182
19bce4d7 TG	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>
2c595172	186
19bce4d7 TG	187	</div><!-- End .main -->
19bce4d7 TG	188	<div class="main">
2c595172	189
19bce4d7 TG	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>
2c595172	195
19bce4d7 TG	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>
2c595172	235
19bce4d7 TG	236	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	237	<div class="section-intro" style="border: none; padding-bottom: 0px;
	238	margin-bottom: 0px;">
2c595172	239
19bce4d7	240	<h2><em>#3</em> Follow the guide as a group</h2>
2c595172	241
19bce4d7 TG	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>
2c595172	249
19bce4d7 TG	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>
2c595172	259
19bce4d7 TG	260	</div><!-- End .section-intro -->
19bce4d7 TG	261	</div></section>
2c595172	262
19bce4d7 TG	263	<!-- ~~~~~~~~~ Section 4: Explain the pitfalls ~~~~~~~~~ -->
19bce4d7 TG	264	<section class="row" id="section4"><div>
2c595172	265
19bce4d7 TG	266	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	267	<div class="section-intro" style="border: none; padding-bottom: 0px;
	268	margin-bottom: 0px;">
2c595172	269
19bce4d7	270	<h2><em>#4</em> Explain the pitfalls</h2>
2c595172	271
19bce4d7 TG	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>
2c595172	276
19bce4d7 TG	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>
2c595172	283
19bce4d7 TG	284	</div><!-- End .section-intro -->
19bce4d7 TG	285	</div></section><!-- End #section4 -->
2c595172	286
19bce4d7 TG	287	<!-- ~~~~~~~~~ Section 5: Explain The Pitfalls ~~~~~~~~~ -->
19bce4d7 TG	288	<section id="section5" class="row"><div>
2c595172	289
19bce4d7 TG	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
f13fb468	300	<a href="https://www.enigmail.net/index.php/documentation">Enigmail's</a>
19bce4d7 TG	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>
2c595172	321
19bce4d7 TG	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 -->
19bce4d7 TG	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 © 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
5dd8f91f TG	346	href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">
5dd8f91f TG	347	source code of Edward reply bot</a> by Andrew Engelbrecht
19bce4d7 TG	348	<sudoman@ninthfloor.org> and Josh Drake <zamnedix@gnu.org>,
	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 & 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ś, <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 -->
7c4f505e	378
5dd8f91f TG	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>
2c595172	383	<!-- Piwik -->
e609e128 AE	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 -->
7c4f505e ZR	403	</body>
7c4f505e ZR	404	</html>