[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 - Teach your friends!</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 - v3.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="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/pump.io.png" class="share-logo"
alt="[Pump.io]" />&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/documentation/index.php">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 -->

<!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
<!-- When un-commenting this section go to main.css and search
for /* Guide Sections Background */ then add #faq to the desired color
<section class="row" id="faq"><div>
<div class="sidebar">

<h2>FAQ</h2>

</div>
<div class="main">

<dl>
<dt>My key expired</dt>
<dd>Answer coming soon.</dd>

<dt>Who can read encrypted messages? Who can read signed ones?</dt>
<dd>Answer coming soon.</dd>

<dt>My email program is opening at times I don't want it to open/is now my
default program and I don't want it to be.</dt>
<dd>Answer coming soon.</dd>
</dl>

</div>
</div>
</section> --><!-- End #faq -->

<!-- ~~~~~~~~~ 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 src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
<script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>

<!-- Piwik -->
<script type="text/javascript" >
// @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-v3-or-Later
var pkBaseURL = (("https:" == document.location.protocol) ? "https://piwik.fsf.org/" : "http://piwik.fsf.org/");
document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));
try {
	var piwikTracker = Piwik.getTracker(pkBaseURL + "piwik.php", 13);
	piwikTracker.trackPageView();
	piwikTracker.enableLinkTracking();
} catch( err ) {}
// @license-end
</script><noscript><p><img src="//piwik.fsf.org/piwik.php?idsite=13" style="border:0" alt="" /></p></noscript>
<!-- End Piwik Tracking Code -->

</body>
</html>
Commit	Line	Data
	1	<!DOCTYPE html>
	2	<html lang="en">
	3	<head>
	4	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
	5	<title>Email Self-Defense - Teach your friends!</title>
	6	<meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy,
	7	email, Enigmail" />
	8	<meta name="description" content="Email surveillance violates our fundamental
	9	rights and makes free speech risky. This guide will teach you email
	10	self-defense in 40 minutes with GnuPG." />
	11	<meta name="viewport" content="width=device-width, initial-scale=1" />
	12	<link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css" />
	13	<link rel="shortcut icon"
	14	href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />
	15	</head>
	16
	17	<body>
	18
	19	<!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
	20	<header class="row" id="header"><div>
	21
	22	<h1>Email Self-Defense</h1>
	23
	24	<!-- Language list for browsers that do not have JS enabled -->
	25	<ul id="languages" class="os">
	26	<li><a class="current" href="/en">English - v4.0</a></li>
	27	<li><a href="/cs">Čeština - v4.0</a></li>
	28	<li><a href="/de">Deutsch - v3.0</a></li>
	29	<li><a href="/el">ελληνικά - v3.0</a></li>
	30	<li><a href="/es">español - v4.0</a></li>
	31	<li><a href="/fa">فارسی - v4.0</a></li>
	32	<li><a href="/fr">français - v4.0</a></li>
	33	<li><a href="/it">italiano - v3.0</a></li>
	34	<li><a href="/ja">日本語 - v4.0</a></li>
	35	<li><a href="/pt-br">português do Brasil - v3.0</a></li>
	36	<li><a href="/ro">română - v3.0</a></li>
	37	<li><a href="/ru">русский - v4.0</a></li>
	38	<li><a href="/sq">Shqip - v4.0</a></li>
	39	<li><a href="/sv">svenska - v4.0</a></li>
	40	<li><a href="/tr">Türkçe - v4.0</a></li>
	41	<li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide"><strong><span
	42	style="color: #2F5FAA;">Translate!</span></strong></a></li>
	43	</ul>
	44
	45	<ul id="menu" class="os">
	46	<li class="spacer"><a href="index.html">GNU/Linux</a></li>
	47	<li><a href="mac.html">Mac OS</a></li>
	48	<li><a href="windows.html">Windows</a></li>
	49	<li><a href="workshops.html" class="current">Teach your friends</a></li>
	50	<li><a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email
	51	encryption for everyone via %40fsf">Share
	52	<img
	53	src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png" class="share-logo"
	54	alt="[GNU Social]" />
	55	<img
	56	src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png" class="share-logo"
	57	alt="[Pump.io]" />
	58	<img
	59	src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png" class="share-logo"
	60	alt="[Reddit]" />
	61	<img
	62	src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png" class="share-logo"
	63	alt="[Hacker News]" />
	64	</a></li>
	65	</ul>
	66
	67	<!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
	68	<div id="fsf-intro">
	69
	70	<h3><a href="http://u.fsf.org/ys"><img
	71	alt="Free Software Foundation"
	72	src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" />
	73	</a></h3>
	74
	75	<div class="fsf-emphasis">
	76
	77	<p>We want to translate this guide
	78	into more languages, and make a version for encryption on mobile
	79	devices. Please donate, and help people around the world take the first
	80	step towards protecting their privacy with free software.</p>
	81
	82	</div>
	83
	84	<p><a
	85	href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img
	86	alt="Donate"
	87	src="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png" /></a></p>
	88
	89	</div><!-- End #fsf-intro -->
	90
	91	<!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
	92	<div class="intro">
	93
	94	<p><a id="infographic"
	95	href="https://emailselfdefense.fsf.org/en/infographic.html"><img
	96	src="//static.fsf.org/nosvn/enc-dev0/img/en/infographic-button.png"
	97	alt="View & share our infographic →" /></a>
	98	Understanding and setting up email encryption sounds like a daunting task
	99	to many people. That's why helping your friends with GnuPG plays such an
	100	important role in helping spread encryption. Even if only one person shows
	101	up, that's still one more person using encryption who wasn't before. You have
	102	the power to help your friends keep their digital love letters private, and
	103	teach them about the importance of free software. If you use GnuPG to send and
	104	receive encrypted email, you're a perfect candidate for leading a workshop!</p>
	105
	106	</div><!-- End .intro -->
	107	</div></header><!-- End #header -->
	108
	109	<!-- ~~~~~~~~~ Section 1: Get your friends or community interested ~~~~~~~~~
	110	-->
	111	<section style="padding-top: 0px;" class="row" id="section1">
	112	<div style="padding-top: 0px;">
	113
	114	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	115	<div class="section-intro">
	116
	117	<p style="margin-top: 0px;" class="image"><img
	118	src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/workshop-section1.png"
	119	alt="A small workshop among friends" /></p>
	120
	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.
	137
	138	<p><img id="workshops-image"
	139	src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/workshop-section1.png"
	140	alt="Workshop icon"></p>-->
	141	</div><!-- /.sidebar -->
	142	<div class="main">
	143
	144	<h3>Strength in numbers</h3>
	145
	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">
	156
	157	<h3>People you respect may already be using encryption</h3>
	158
	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>
	164
	165	</div><!-- End .main -->
	166	<div class="main">
	167
	168	<h3>Respect your friends' privacy</h3>
	169
	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>
	175
	176	</div><!-- End .main -->
	177	<div class="main">
	178
	179	<h3>Privacy technology is normal in the physical world</h3>
	180
	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>
	184
	185	</div><!-- End .main -->
	186	<div class="main">
	187
	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>
	193
	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
	210	participants to use Diceware for choosing passwords, get a pack of dice
	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
	215	an Enigmail-compatible email client before the event. Direct them to their
	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>
	233
	234	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	235	<div class="section-intro" style="border: none; padding-bottom: 0px;
	236	margin-bottom: 0px;">
	237
	238	<h2><em>#3</em> Follow the guide as a group</h2>
	239
	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>
	247
	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>
	257
	258	</div><!-- End .section-intro -->
	259	</div></section>
	260
	261	<!-- ~~~~~~~~~ Section 4: Explain the pitfalls ~~~~~~~~~ -->
	262	<section class="row" id="section4"><div>
	263
	264	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	265	<div class="section-intro" style="border: none; padding-bottom: 0px;
	266	margin-bottom: 0px;">
	267
	268	<h2><em>#4</em> Explain the pitfalls</h2>
	269
	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>
	274
	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>
	281
	282	</div><!-- End .section-intro -->
	283	</div></section><!-- End #section4 -->
	284
	285	<!-- ~~~~~~~~~ Section 5: Explain The Pitfalls ~~~~~~~~~ -->
	286	<section id="section5" class="row"><div>
	287
	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
	297	<a href="https://www.gnupg.org/documentation/index.html">GnuPG's</a> and
	298	<a href="https://www.enigmail.net/documentation/index.php">Enigmail's</a>
	299	official documentation and mailing lists. Many GNU/Linux distribution's Web
	300	sites also contain a page explaining some of GnuPG's advanced features.</p>
	301
	302	</div><!-- End .section-intro -->
	303	</div></section><!-- End #section5 -->
	304
	305	<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
	306	<section class="row" id="section6"><div>
	307
	308	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	309	<div class="section-intro" style="border: none; padding-bottom: 0px;
	310	margin-bottom: 0px;">
	311
	312	<h2><em>#6</em> Follow up</h2>
	313
	314	<p>Make sure everyone has shared email addresses and public key fingerprints
	315	before they leave. Encourage the participants to continue to gain GnuPG
	316	experience by emailing each other. Send them each an encrypted email one
	317	week after the event, reminding them to try adding their public key ID to
	318	places where they publicly list their email address.</p>
	319
	320	<p>If you have any suggestions for improving this workshop guide, please
	321	let us know at <a href="mailto:campaigns@fsf.org">campaigns@fsf.org</a>.</p>
	322
	323	</div><!-- End .section-intro -->
	324	</div></section><!-- End #section6 -->
	325
	326	<!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
	327	<!-- When un-commenting this section go to main.css and search
	328	for /* Guide Sections Background */ then add #faq to the desired color
	329	<section class="row" id="faq"><div>
	330	<div class="sidebar">
	331
	332	<h2>FAQ</h2>
	333
	334	</div>
	335	<div class="main">
	336
	337	<dl>
	338	<dt>My key expired</dt>
	339	<dd>Answer coming soon.</dd>
	340
	341	<dt>Who can read encrypted messages? Who can read signed ones?</dt>
	342	<dd>Answer coming soon.</dd>
	343
	344	<dt>My email program is opening at times I don't want it to open/is now my
	345	default program and I don't want it to be.</dt>
	346	<dd>Answer coming soon.</dd>
	347	</dl>
	348
	349	</div>
	350	</div>
	351	</section> --><!-- End #faq -->
	352
	353	<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
	354	<footer class="row" id="footer"><div>
	355	<div id="copyright">
	356
	357	<h4><a href="https://u.fsf.org/ys"><img
	358	alt="Free Software Foundation"
	359	src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png" /></a></h4>
	360
	361	<p>Copyright © 2014-2016 <a
	362	href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a
	363	href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. Please
	364	support our work by <a href="https://u.fsf.org/yr">joining us as an associate
	365	member.</a></p>
	366
	367	<p>The images on this page are under a <a
	368	href="https://creativecommons.org/licenses/by/4.0/">Creative Commons
	369	Attribution 4.0 license (or later version)</a>, and the rest of it is under
	370	a <a href="https://creativecommons.org/licenses/by-sa/4.0">Creative Commons
	371	Attribution-ShareAlike 4.0 license (or later version)</a>. Download the <a
	372	href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">source
	373	code of Edward reply bot</a> by Andrew Engelbrecht
	374	<sudoman@ninthfloor.org> and Josh Drake <zamnedix@gnu.org>,
	375	available under the GNU Affero General Public License. <a
	376	href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these
	377	licenses?</a></p>
	378
	379	<p>Fonts used in the guide & infographic: <a
	380	href="https://www.google.com/fonts/specimen/Dosis">Dosis</a> by Pablo
	381	Impallari, <a href="http://www.google.com/fonts/specimen/Signika">Signika</a>
	382	by Anna Giedryś, <a
	383	href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo
	384	Narrow</a> by Omnibus-Type, <a
	385	href="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a>
	386	by Florian Cramer.</p>
	387
	388	<p>Download the <a href="emailselfdefense_source.zip">source package</a>
	389	for this guide, including fonts, image source files and the text of Edward's
	390	messages.</p>
	391
	392	<p>This site uses the Weblabels standard for labeling <a
	393	href="https://www.fsf.org/campaigns/freejs">free JavaScript</a>. View
	394	the JavaScript <a href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
	395	rel="jslicense">source code and license information</a>.</p>
	396
	397	</div><!-- /#copyright -->
	398
	399	<p class="credits">Infographic and guide design by <a rel="external"
	400	href="http://jplusplus.org"><strong>Journalism++</strong><img
	401	src="//static.fsf.org/nosvn/enc-dev0/img/jplusplus.png"
	402	alt="Journalism++" /></a></p><!-- /.credits -->
	403	</div></footer><!-- End #footer -->
	404
	405	<script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
	406	<script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
	407
	408	<!-- Piwik -->
	409	<script type="text/javascript" >
	410	// @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-v3-or-Later
	411	var pkBaseURL = (("https:" == document.location.protocol) ? "https://piwik.fsf.org/" : "http://piwik.fsf.org/");
	412	document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));
	413	try {
	414	var piwikTracker = Piwik.getTracker(pkBaseURL + "piwik.php", 13);
	415	piwikTracker.trackPageView();
	416	piwikTracker.enableLinkTracking();
	417	} catch( err ) {}
	418	// @license-end
	419	</script><noscript><p><img src="//piwik.fsf.org/piwik.php?idsite=13" style="border:0" alt="" /></p></noscript>
	420	<!-- End Piwik Tracking Code -->
	421
	422	</body>
	423	</html>