[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/css/main.css" />
<link rel="shortcut icon"
href="/static/img/favicon.ico" />
</head>

<body><iframe src="https://static.fsf.org/nosvn/banners/2021fundraiser-spring/" style="width: 100%; height: 150px; display: block; margin: 0; border: 0 none; overflow: hidden;"></iframe><div style="text-align: center; padding: 2.5px; background-color: #a94442; color:#fcf8e3;"><p>Due to Enigmail's PGP functionality being migrated into Icedove and Thunderbird, steps 2 and 3 of the guide are currently out of date.</p><p> Thank you for your patience while we're working on a new round of updates.</p></div>

<!-- ~~~~~~~~~ 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/img/gnu-social.png" class="share-logo"
alt="[GNU Social]" />&nbsp;
<img
src="/static/img/mastodon.png" class="share-logo"
alt="[Mastodon]" />&nbsp;
<img
src="/static/img/reddit-alien.png" class="share-logo"
alt="[Reddit]" />&nbsp;
<img
src="/static/img/hacker-news.png" class="share-logo"
alt="[Hacker News]" />
</a></li>
</ul>

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

<h3><a href="https://u.fsf.org/ys"><img
alt="Free Software Foundation"
src="/static/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/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/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/img/en/screenshots/workshop-section1-update.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/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 <a href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">Diceware</a> 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 email client based on Thunderbird 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> 
official documentation and mailing lists, and the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Email Self-Defense feedback</a> page. 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/img/fsf-logo.png" /></a></h4>

<p>Copyright &copy; 2014-2021 <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="https://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">
source code of Edward reply bot</a> by Andrew Engelbrecht
&lt;andrew@engelbrecht.io&gt; and Josh Drake &lt;zamnedix@gnu.org&gt;,
available under the GNU Affero General Public License. <a
href="https://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="https://www.google.com/fonts/specimen/Signika">Signika</a>
by Anna Giedry&#347;, <a
href="https://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="https://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="https://jplusplus.org"><strong>Journalism++</strong><img
src="/static/img/jplusplus.png"
alt="Journalism++" /></a></p><!-- /.credits -->
</div></footer><!-- End #footer -->

<script type="text/javascript"
src="/static/js/jquery-1.11.0.min.js"></script>
<script type="text/javascript"
<!-- 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" />
812ccf00	13	<link rel="stylesheet" href="/static/css/main.css" />
19bce4d7	14	<link rel="shortcut icon"
812ccf00	15	href="/static/img/favicon.ico" />
2c595172	16	</head>
19bce4d7	17
abf30801	18	<body><iframe src="https://static.fsf.org/nosvn/banners/2021fundraiser-spring/" style="width: 100%; height: 150px; display: block; margin: 0; border: 0 none; overflow: hidden;"></iframe><div style="text-align: center; padding: 2.5px; background-color: #a94442; color:#fcf8e3;"><p>Due to Enigmail's PGP functionality being migrated into Icedove and Thunderbird, steps 2 and 3 of the guide are currently out of date.</p><p> Thank you for your patience while we're working on a new round of updates.</p></div>
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">
810614f7	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>
810614f7	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
812ccf00	55	src="/static/img/gnu-social.png" class="share-logo"
19bce4d7 TG	56	alt="[GNU Social]" />
19bce4d7 TG	57	<img
812ccf00	58	src="/static/img/mastodon.png" class="share-logo"
d06ce723	59	alt="[Mastodon]" />
19bce4d7	60	<img
812ccf00	61	src="/static/img/reddit-alien.png" class="share-logo"
19bce4d7 TG	62	alt="[Reddit]" />
19bce4d7 TG	63	<img
812ccf00	64	src="/static/img/hacker-news.png" class="share-logo"
19bce4d7 TG	65	alt="[Hacker News]" />
	66	</a></li>
	67	</ul>
	68
	69	<!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
	70	<div id="fsf-intro">
	71
6003a573	72	<h3><a href="https://u.fsf.org/ys"><img
19bce4d7	73	alt="Free Software Foundation"
812ccf00	74	src="/static/img/fsf-logo.png" />
19bce4d7 TG	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"
812ccf00	89	src="/static/img/en/donate.png" /></a></p>
19bce4d7 TG	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
812ccf00	98	src="/static/img/en/infographic-button.png"
19bce4d7 TG	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">
19bce4d7	118	<p style="margin-top: 0px;" class="image"><img
812ccf00	119	src="/static/img/en/screenshots/workshop-section1-update.png"
19bce4d7	120	alt="A small workshop among friends" /></p>
19bce4d7 TG	121	<h2><em>#1</em> Get your friends or community interested </h2>
	122
	123	<p>If you hear friends grumbling about their lack of privacy, ask them if
	124	they're interested in attending a workshop on Email Self-Defense. If your
	125	friends don't grumble about privacy, they may need some convincing. You might
	126	even hear the classic "if you've got nothing to hide, you've got nothing to
	127	fear" argument against using encryption.</p>
	128
	129	<p>Here are some talking points you can use to help explain why it's worth
	130	it to learn GnuPG. Mix and match whichever you think will make sense to
	131	your community:</p>
	132
	133	</div><!-- End .section-intro -->
	134	<div id="step-aa" class="step">
	135	<div class="sidebar">
	136	<!-- Workshops image commented out from here, to be used above instead.
2c595172	137
19bce4d7	138	<p><img id="workshops-image"
812ccf00	139	src="/static/img/en/screenshots/workshop-section1.png"
19bce4d7 TG	140	alt="Workshop icon"></p>-->
	141	</div><!-- /.sidebar -->
	142	<div class="main">
2c595172	143
19bce4d7	144	<h3>Strength in numbers</h3>
2c595172	145
19bce4d7 TG	146	<p>Each person who chooses to resist mass surveillance with encryption makes
	147	it easier for others to resist as well. People normalizing the use of strong
	148	encryption has multiple powerful effects: it means those who need privacy
	149	the most, like potential whistle-blowers and activists, are more likely to
	150	learn about encryption. More people using encryption for more things also
	151	makes it harder for surveillance systems to single out those that can't
	152	afford to be found, and shows solidarity with those people.</p>
	153
	154	</div><!-- End .main -->
	155	<div class="main">
2c595172	156
19bce4d7	157	<h3>People you respect may already be using encryption</h3>
d083698e	158
19bce4d7 TG	159	<p>Many journalists, whistleblowers, activists, and researchers use GnuPG,
	160	so your friends might unknowingly have heard of a few people who use it
	161	already. You can search for "BEGIN PUBLIC KEY BLOCK" + keyword to help make
	162	a list of people and organizations who use GnuPG whom your community will
	163	likely recognize.</p>
2c595172	164
19bce4d7 TG	165	</div><!-- End .main -->
19bce4d7 TG	166	<div class="main">
2c595172	167
19bce4d7	168	<h3>Respect your friends' privacy</h3>
2c595172	169
19bce4d7 TG	170	<p>There's no objective way to judge what constitutes privacy-sensitive
	171	correspondence. As such, it's better not to presume that just because you
	172	find an email you sent to a friend innocuous, your friend (or a surveillance
	173	agent, for that matter!) feels the same way. Show your friends respect by
	174	encrypting your correspondence with them.</p>
2c595172	175
19bce4d7 TG	176	</div><!-- End .main -->
19bce4d7 TG	177	<div class="main">
2c595172	178
19bce4d7	179	<h3>Privacy technology is normal in the physical world</h3>
2c595172	180
19bce4d7 TG	181	<p>In the physical realm, we take window blinds, envelopes, and closed doors
	182	for granted as ways of protecting our privacy. Why should the digital realm
	183	be any different?</p>
2c595172	184
19bce4d7 TG	185	</div><!-- End .main -->
19bce4d7 TG	186	<div class="main">
2c595172	187
19bce4d7 TG	188	<h3>We shouldn't have to trust our email providers with our privacy</h3>
	189
	190	<p>Some email providers are very trustworthy, but many have incentives not
	191	to protect your privacy and security. To be empowered digital citizens,
	192	we need to build our own security from the bottom up.</p>
2c595172	193
19bce4d7 TG	194	</div><!-- End .main -->
	195	</div><!-- End #step-aa .step -->
	196	</div></section><!-- End #section1 -->
	197
	198	<!-- ~~~~~~~~~ Section 2: Plan The Workshop ~~~~~~~~~ -->
	199	<section class="row" id="section2"><div>
	200
	201	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	202	<div class="section-intro" style="border: none; padding-bottom: 0px;
	203	margin-bottom: 0px;">
	204
	205	<h2><em>#2</em> Plan The Workshop</h2>
	206
	207	<p>Once you've got at least one interested friend, pick a date and start
	208	planning out the workshop. Tell participants to bring their computer and
	209	ID (for signing each other's keys). If you'd like to make it easy for the
2e2151c8	210	participants to use <a href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">Diceware</a> for choosing passwords, get a pack of dice
19bce4d7 TG	211	beforehand. Make sure the location you select has an easily accessible
	212	Internet connection, and make backup plans in case the connection stops
	213	working on the day of the workshop. Libraries, coffee shops, and community
	214	centers make great locations. Try to get all the participants to set up
2e2151c8	215	an email client based on Thunderbird before the event. Direct them to their
19bce4d7 TG	216	email provider's IT department or help page if they run into errors.</p>
	217
	218	<p>Estimate that the workshop will take at least forty minutes plus ten minutes
	219	for each participant. Plan extra time for questions and technical glitches.</p>
	220
	221	<p>The success of the workshop requires understanding and catering to
	222	the unique backgrounds and needs of each group of participants. Workshops
	223	should stay small, so that each participant receives more individualized
	224	instruction. If more than a handful of people want to participate, keep the
	225	facilitator to participant ratio high by recruiting more facilitators, or by
	226	facilitating multiple workshops. Small workshops among friends work great!</p>
	227
	228	</div><!-- End .section-intro -->
	229	</div></section><!-- End #section2 -->
	230
	231	<!-- ~~~~~~~~~ Section 3: Follow The Guide ~~~~~~~~~ -->
	232	<section class="row" id="section3"><div>
2c595172	233
19bce4d7 TG	234	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	235	<div class="section-intro" style="border: none; padding-bottom: 0px;
	236	margin-bottom: 0px;">
2c595172	237
19bce4d7	238	<h2><em>#3</em> Follow the guide as a group</h2>
2c595172	239
19bce4d7 TG	240	<p>Work through the Email Self-Defense guide a step at a time as a group. Talk
	241	about the steps in detail, but make sure not to overload the participants
	242	with minutia. Pitch the bulk of your instructions to the least tech-savvy
	243	participants. Make sure all the participants complete each step before the
	244	group moves on to the next one. Consider facilitating secondary workshops
	245	afterwards for people that had trouble grasping the concepts, or those that
	246	grasped them quickly and want to learn more.</p>
2c595172	247
19bce4d7 TG	248	<p>In <a href="index.html#section2">Section 2</a> of the guide, make
	249	sure the participants upload their keys to the same keyserver so that
	250	they can immediately download each other's keys later (sometimes
	251	there is a delay in synchronization between keyservers). During <a
	252	href="index.html#section3">Section 3</a>, give the participants the option to
	253	send test messages to each other instead of or as well as Edward. Similarly,
	254	in <a href="index.html#section4">Section 4</a>, encourage the participants
	255	to sign each other's keys. At the end, make sure to remind people to safely
	256	back up their revocation certificates.</p>
2c595172	257
19bce4d7 TG	258	</div><!-- End .section-intro -->
19bce4d7 TG	259	</div></section>
2c595172	260
19bce4d7 TG	261	<!-- ~~~~~~~~~ Section 4: Explain the pitfalls ~~~~~~~~~ -->
19bce4d7 TG	262	<section class="row" id="section4"><div>
2c595172	263
19bce4d7 TG	264	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	265	<div class="section-intro" style="border: none; padding-bottom: 0px;
	266	margin-bottom: 0px;">
2c595172	267
19bce4d7	268	<h2><em>#4</em> Explain the pitfalls</h2>
2c595172	269
19bce4d7 TG	270	<p>Remind participants that encryption works only when it's explicitly used;
	271	they won't be able to send an encrypted email to someone who hasn't already
	272	set up encryption. Also remind participants to double-check the encryption icon
	273	before hitting send, and that subjects and timestamps are never encrypted.</p>
2c595172	274
19bce4d7 TG	275	<p> Explain the <a
	276	href="https://www.gnu.org/proprietary/proprietary.html">dangers
	277	of running a proprietary system</a> and
	278	advocate for free software, because without it, we can't <a
	279	href="https://www.fsf.org/bulletin/2013/fall/how-can-free-software-protect-us-from-surveillance">meaningfully
	280	resist invasions of our digital privacy and autonomy</a>.</p>
2c595172	281
19bce4d7 TG	282	</div><!-- End .section-intro -->
19bce4d7 TG	283	</div></section><!-- End #section4 -->
2c595172	284
19bce4d7 TG	285	<!-- ~~~~~~~~~ Section 5: Explain The Pitfalls ~~~~~~~~~ -->
19bce4d7 TG	286	<section id="section5" class="row"><div>
2c595172	287
19bce4d7 TG	288	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	289	<div class="section-intro" style="border: none; padding-bottom: 0px;
	290	margin-bottom: 0px;">
	291
	292	<h2><em>#5</em> Share additional resources</h2>
	293
	294	<p>GnuPG's advanced options are far too complex to teach in a single
	295	workshop. If participants want to know more, point out the advanced subsections
	296	in the guide and consider organizing another workshop. You can also share
2e2151c8	297	<a href="https://www.gnupg.org/documentation/index.html">GnuPG's</a>
2e2151c8	298	official documentation and mailing lists, and the <a href="https://libreplanet.org/wiki/GPG_guide/Public_Review">Email Self-Defense feedback</a> page. Many GNU/Linux distribution's Web
19bce4d7 TG	299	sites also contain a page explaining some of GnuPG's advanced features.</p>
	300
	301	</div><!-- End .section-intro -->
	302	</div></section><!-- End #section5 -->
	303
	304	<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
	305	<section class="row" id="section6"><div>
	306
	307	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	308	<div class="section-intro" style="border: none; padding-bottom: 0px;
	309	margin-bottom: 0px;">
	310
	311	<h2><em>#6</em> Follow up</h2>
	312
	313	<p>Make sure everyone has shared email addresses and public key fingerprints
	314	before they leave. Encourage the participants to continue to gain GnuPG
	315	experience by emailing each other. Send them each an encrypted email one
	316	week after the event, reminding them to try adding their public key ID to
	317	places where they publicly list their email address.</p>
2c595172	318
19bce4d7 TG	319	<p>If you have any suggestions for improving this workshop guide, please
	320	let us know at <a href="mailto:campaigns@fsf.org">campaigns@fsf.org</a>.</p>
	321
	322	</div><!-- End .section-intro -->
	323	</div></section><!-- End #section6 -->
19bce4d7 TG	324	<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
	325	<footer class="row" id="footer"><div>
	326	<div id="copyright">
	327
	328	<h4><a href="https://u.fsf.org/ys"><img
	329	alt="Free Software Foundation"
812ccf00	330	src="/static/img/fsf-logo.png" /></a></h4>
19bce4d7	331
2e2151c8	332	<p>Copyright © 2014-2021 <a
19bce4d7 TG	333	href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a
	334	href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please
	335	support our work by <a href="https://u.fsf.org/yr">joining us as an associate
	336	member.</a></p>
	337
	338	<p>The images on this page are under a <a
	339	href="https://creativecommons.org/licenses/by/4.0/">Creative Commons
	340	Attribution 4.0 license (or later version)</a>, and the rest of it is under
	341	a <a href="https://creativecommons.org/licenses/by-sa/4.0">Creative Commons
	342	Attribution-ShareAlike 4.0 license (or later version)</a>. Download the <a
6003a573	343	href="https://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">
5dd8f91f	344	source code of Edward reply bot</a> by Andrew Engelbrecht
a3a9a0ac	345	<andrew@engelbrecht.io> and Josh Drake <zamnedix@gnu.org>,
19bce4d7	346	available under the GNU Affero General Public License. <a
6003a573	347	href="https://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these
19bce4d7 TG	348	licenses?</a></p>
	349
	350	<p>Fonts used in the guide & infographic: <a
	351	href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> by Pablo
6003a573	352	Impallari, <a href="https://www.google.com/fonts/specimen/Signika">Signika</a>
19bce4d7	353	by Anna Giedryś, <a
6003a573	354	href="https://www.google.com/fonts/specimen/Archivo+Narrow">Archivo
19bce4d7 TG	355	Narrow</a> by Omnibus-Type, <a
	356	href="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a>
	357	by Florian Cramer.</p>
	358
	359	<p>Download the <a href="emailselfdefense_source.zip">source package</a>
	360	for this guide, including fonts, image source files and the text of Edward's
	361	messages.</p>
	362
	363	<p>This site uses the Weblabels standard for labeling <a
	364	href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View
abf30801	365	the JavaScript <a href="https://weblabels.fsf.org/emailselfdefense.fsf.org/"
19bce4d7 TG	366	rel="jslicense">source code and license information</a>.</p>
	367
	368	</div><!-- /#copyright -->
	369
	370	<p class="credits">Infographic and guide design by <a rel="external"
6003a573	371	href="https://jplusplus.org"><strong>Journalism++</strong><img
812ccf00	372	src="/static/img/jplusplus.png"
19bce4d7 TG	373	alt="Journalism++" /></a></p><!-- /.credits -->
19bce4d7 TG	374	</div></footer><!-- End #footer -->
7c4f505e	375
5dd8f91f	376	<script type="text/javascript"
812ccf00	377	src="/static/js/jquery-1.11.0.min.js"></script>
5dd8f91f	378	<script type="text/javascript"
2c595172	379	<!-- Piwik -->
e609e128 AE	380	<script type="text/javascript">
	381	// @license magnet:?xt=urn:btih:cf05388f2679ee054f2beb29a391d25f4e673ac3&dn=gpl-2.0.txt GPL-2.0-or-later
	382	var _paq = _paq \|\| [];
	383	_paq.push(["trackPageView"]);
	384	_paq.push(["enableLinkTracking"]);
	385
	386	(function() {
	387	var u = (("https:" == document.location.protocol) ? "https" : "http") + "://"+"piwik.fsf.org//";
	388	_paq.push(["setTrackerUrl", u+"piwik.php"]);
	389	_paq.push(["setSiteId", "13"]);
	390	var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
	391	g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
	392	})();
	393	// @license-end
	394	</script>
	395	<!-- End Piwik Code -->
	396	<!-- Piwik Image Tracker -->
	397	<noscript><img src="https://piwik.fsf.org//piwik.php?idsite=13&rec=1" style="border:0" alt="" /></noscript>
	398	<!-- End Piwik -->
7c4f505e ZR	399	</body>
7c4f505e ZR	400	</html>