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

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

			<!-- Languages removed until we have translations-->

			<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 class="spacer"><a href="workshops.html" class="current">Teach your friends</a></li>
				<li class="spacer">
					<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>
				<li class="spacer">V4.0</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 fight for computer users'
						rights, and promote the development of free (as in freedom) software.
						Resisting bulk surveillance is very important to us.
					</p>
					<p>
						<strong>
							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.
						</strong>
					</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>
				</p><p>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"></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 arguments 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 that truly need privacy, 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 which 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 a 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 correspondences 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><!-- End #step-2a .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). Also tell the participants to bring dice (for making passwords), but also bring as many as you can, in case they don't. 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>
				</p><p>Estimate that the workshop will take forty minutes plus ten minutes for each participant, at a minimum. 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 low 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 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>Even powerful surveillance systems can't break private keys when they're protected by lengthy Diceware passphrases. Make sure participants use the Diceware method, if dice are available. Stress the importance of eventually destroying the piece of paper the Diceware password is written on, and make sure all the participants back up their revocation certificates.</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 encrypted 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.</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. See the guide's <a href="index.html#step-headers_unencrypted">Security Tips</a> subsection for more information.</p>
				<p>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>. Explain the <a href="https://www.gnu.org/proprietary/proprietary.html">dangers of running a proprietary system</a>, and why GnuPG <a href="https://www.gnu.org/philosophy/proprietary-surveillance.html">can't begin to mitigate them</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>Encourage the participants to continue to gain GnuPG experience by emailing each other, and considering offering to correspond with them in encrypted form. If you don't hear from them for a couple of weeks after the event, reach out and see if they would like additional assistance.</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 © 2014-2015 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. <a href="https://u.fsf.org/yr">Join.</a></p>
			<p><em><a href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">Source code of Edward reply bot by Josh Drake &lt;zamnedix@gnu.org&gt; available under the GNU General Public License.</a></em></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>. — <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>
			<p>Download the source package for <a href="emailselfdefense_source.zip">this guide</a>. 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ś, <a href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> by Omnibus-Type, <a href="http://www.thegopherarchive.com/gopher-files-hacks-pxl2000-119351.htm">PXL-2000</a> by Florian Cramer.</p>
			<p>
				<a href="//weblabels.fsf.org/emailselfdefense.fsf.org/" rel="jslicense">
					JavaScript 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="http://piwik.fsf.org/piwik.js" async="" defer="" type="text/javascript"></script><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">
	/*
	@licstart The following is the entire license notice for the
	JavaScript code in this page.

	Copyright 2014 Matthieu Aubry

	This program is free software: you can redistribute it and/or modify
	it under the terms of the GNU General Public License as published by
	the Free Software Foundation, either version 3 of the License, or
	(at your option) any later version.

	This program is distributed in the hope that it will be useful,
	but WITHOUT ANY WARRANTY; without even the implied warranty of
	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
	GNU General Public License for more details.

	You should have received a copy of the GNU General Public License
	along with this program.  If not, see http://www.gnu.org/licenses/.

	@licend The above is the entire license notice
	for the JavaScript code in this page.
	*/
	var _paq = _paq || [];
	_paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
	_paq.push(["setCookieDomain", "*.www.fsf.org"]);
	_paq.push(["setDomains", ["*.www.fsf.org","*.www.fsf.org"]]);
	_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", "5"]);
		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);
	})();
</script>
<!-- End Piwik Code -->


</body></html>
Commit	Line	Data
1c4bff08 ZR	1	<html><head>
	2	<meta http-equiv="content-type" content="text/html; charset=utf-8">
	3
	4	<title>Email Self-Defense - Teach your friends!</title>
	5	<meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy, email, Enigmail">
	6	<meta name="description" content="Email surveillance violates our fundamental rights and makes free speech risky. This guide will teach you email self-defense in 30 minutes with GnuPG.">
	7
	8	<meta name="viewport" content="width=device-width, initial-scale=1">
	9	<link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css">
	10	<link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico">
	11
	12	</head>
	13	<body>
	14
	15	<!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
	16
	17	<header class="row" id="header">
	18	<div>
	19	<h1>Email Self-Defense</h1>
	20
	21	<!-- Languages removed until we have translations-->
	22
	23	<ul id="menu" class="os">
	24	<li class="spacer">
	25	<a href="index.html">GNU/Linux</a>
	26	</li>
	27	<li>
	28	<a href="mac.html">Mac OS</a>
	29	</li>
	30	<li>
	31	<a href="windows.html">Windows</a>
	32	</li>
	33	<li class="spacer"><a href="workshops.html" class="current">Teach your friends</a></li>
	34	<li class="spacer">
	35	<a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email encryption for everyone via %40fsf">
	36	Share
	37	<img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png" class="share-logo" alt="[GNU Social]">
	38	<img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png" class="share-logo" alt="[Pump.io]">
	39	<img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png" class="share-logo" alt="[Reddit]">
	40	<img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png" class="share-logo" alt="[Hacker News]">
	41	</a>
	42	</li>
	43	<li class="spacer">V4.0</li>
	44	</ul>
	45	<!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
	46	<div id="fsf-intro">
	47	<h3>
	48	<a href="http://u.fsf.org/ys">
	49	<img alt="Free Software Foundation" src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png">
	50	</a>
	51	</h3>
	52	<div class="fsf-emphasis">
b592e92f	53	<p>
1c4bff08 ZR	54	We fight for computer users'
	55	rights, and promote the development of free (as in freedom) software.
	56	Resisting bulk surveillance is very important to us.
	57	</p>
	58	<p>
	59	<strong>
	60	We want to translate this guide
	61	into more languages, and make a version for encryption on mobile
	62	devices. Please donate, and help people around the world take the first
	63	step towards protecting their privacy with free software.
	64	</strong>
	65	</p>
	66	</div>
b592e92f	67
1c4bff08	68	<p><a href="https://crm.fsf.org/civicrm/contribute/transact?reset=1&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img alt="Donate" src="//static.fsf.org/nosvn/enc-dev0/img/en/donate.png"></a> </p>
b592e92f	69
1c4bff08	70	</div><!-- End #fsf-intro -->
b592e92f	71
1c4bff08 ZR	72	<!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
	73	<div class="intro">
	74	<p>
	75	<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 & share our infographic →"></a>
	76	</p><p>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>
22e76ed5	77
1c4bff08	78	</div><!-- End .intro -->
b592e92f	79
1c4bff08 ZR	80	</div>
1c4bff08 ZR	81	</header><!-- End #header -->
c8a179b6	82
1c4bff08 ZR	83	<!-- ~~~~~~~~~ Section 1: Get your friends or community interested> ~~~~~~~~~ -->
	84	<section style="padding-top: 0px;" class="row" id="section1">
	85	<div style="padding-top: 0px;">
55224049	86
1c4bff08 ZR	87	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	88	<div class="section-intro">
	89	<p style="margin-top: 0px;" class="image"><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/workshop-section1.png"></p>
	90	<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>
	91	<p>Here are some arguments 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>
55224049	92
1c4bff08	93	</div><!-- End .section-intro -->
d4a7d4c9	94
1c4bff08	95	<div id="step-aa" class="step">
9fcfafe0	96
d4a7d4c9	97
1c4bff08 ZR	98	<div class="sidebar">
	99	<!-- Workshops image commented out from here, to be used above instead.
	100	<p><img id="workshops-image" src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/workshop-section1.png" alt="Workshop icon"></p>-->
	101	</div><!-- /.sidebar -->
d4a7d4c9	102
1c4bff08 ZR	103	<div class="main">
	104	<h3>Strength in numbers</h3>
	105	<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 that truly need privacy, 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>
	106	</div><!-- End .main -->
d4a7d4c9	107
1c4bff08 ZR	108	<div class="main">
	109	<h3>People you respect may already be using encryption</h3>
	110	<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 which your community will likely recognize.</p>
	111	</div><!-- End .main -->
d4a7d4c9	112
1c4bff08 ZR	113	<div class="main">
	114	<h3>Respect your friends' privacy</h3>
	115	<p>There's no objective way to judge what constitutes a 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 correspondences with them.</p>
	116	</div><!-- End .main -->
c8a179b6	117
b592e92f	118
1c4bff08 ZR	119	<div class="main">
	120	<h3>Privacy technology is normal in the physical world</h3>
	121	<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>
	122	</div><!-- End .main -->
b592e92f	123
b592e92f	124
1c4bff08	125	</div><!-- End #step-2a .step -->
1dd9bd62	126
1c4bff08 ZR	127	</div>
1c4bff08 ZR	128	</section><!-- End #section1 -->
b592e92f	129
1c4bff08 ZR	130	<!-- ~~~~~~~~~ Section 2: Plan The Workshop ~~~~~~~~~ -->
	131	<section class="row" id="section2">
	132	<div>
	133	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	134	<div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
	135	<h2><em>#2</em> Plan The Workshop</h2>
	136	<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). Also tell the participants to bring dice (for making passwords), but also bring as many as you can, in case they don't. 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>
	137	</p><p>Estimate that the workshop will take forty minutes plus ten minutes for each participant, at a minimum. Plan extra time for questions and technical glitches.</p>
	138	<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 low by recruiting more facilitators, or by facilitating multiple workshops. Small workshops among friends work great!</p>
b592e92f	139
b592e92f	140
1c4bff08	141	</div><!-- End .section-intro -->
b592e92f	142
1c4bff08 ZR	143	</div>
1c4bff08 ZR	144	</section><!-- End #section2 -->
b592e92f	145
1c4bff08 ZR	146	<!-- ~~~~~~~~~ Section 3: Follow The Guide ~~~~~~~~~ -->
	147	<section class="row" id="section3">
	148	<div>
	149	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	150	<div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
	151	<h2><em>#3</em> Follow the guide as a group</h2>
	152	<p>Work through the Email Self-Defense guide a step at 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>
	153	<p>Even powerful surveillance systems can't break private keys when they're protected by lengthy Diceware passphrases. Make sure participants use the Diceware method, if dice are available. Stress the importance of eventually destroying the piece of paper the Diceware password is written on, and make sure all the participants back up their revocation certificates.</p>
	154	<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 encrypted 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.</p>
b592e92f	155
1c4bff08 ZR	156	</div><!-- End .section-intro -->
	157	</div>
	158	</section>
b592e92f	159
b592e92f	160
1c4bff08 ZR	161	<!-- ~~~~~~~~~ Section 4: Explain the pitfalls ~~~~~~~~~ -->
	162	<section class="row" id="section4">
	163	<div>
	164	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	165	<div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
	166	<h2><em>#4</em> Explain the pitfalls</h2>
	167	<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. See the guide's <a href="index.html#step-headers_unencrypted">Security Tips</a> subsection for more information.</p>
	168	<p>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>. Explain the <a href="https://www.gnu.org/proprietary/proprietary.html">dangers of running a proprietary system</a>, and why GnuPG <a href="https://www.gnu.org/philosophy/proprietary-surveillance.html">can't begin to mitigate them</a>.</p>
b592e92f	169
b592e92f	170
b592e92f	171
1c4bff08	172	</div><!-- End .section-intro -->
b592e92f	173
1c4bff08 ZR	174	</div>
1c4bff08 ZR	175	</section><!-- End #section4 -->
b592e92f	176
1c4bff08 ZR	177	<!-- ~~~~~~~~~ Section 5: Explain The Pitfalls ~~~~~~~~~ -->
	178	<section id="section5" class="row">
	179	<div>
	180	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	181	<div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
	182	<h2><em>#5</em> Share additional resources</h2>
	183	<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>
b592e92f	184
1c4bff08	185	</div><!-- End .section-intro -->
b592e92f	186
b592e92f	187
1c4bff08 ZR	188	</div>
1c4bff08 ZR	189	</section><!-- End #section5 -->
b592e92f	190
da96bef7	191
b592e92f	192
1c4bff08 ZR	193	<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
	194	<section class="row" id="section6">
	195	<div>
	196	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	197	<div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
	198	<h2><em>#6</em> Follow up</h2>
	199	<p>Encourage the participants to continue to gain GnuPG experience by emailing each other, and considering offering to correspond with them in encrypted form. If you don't hear from them for a couple of weeks after the event, reach out and see if they would like additional assistance.</p>
	200	<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>
b592e92f	201
1c4bff08	202	</div><!-- End .section-intro -->
b592e92f	203
b592e92f	204
1c4bff08 ZR	205	</div>
1c4bff08 ZR	206	</section><!-- End #section6 -->
b592e92f	207
1c4bff08 ZR	208	<!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
	209	<!-- When un-commenting this section go to main.css and search
	210	for /* Guide Sections Background */ then add #faq to the desired color
	211
	212	<section class="row" id="faq">
	213	<div>
	214	<div class="sidebar">
	215	<h2>FAQ</h2>
	216	</div>
	217
	218	<div class="main">
	219	<dl>
	220	<dt>My key expired</dt>
	221	<dd>Answer coming soon.</dd>
	222
	223	<dt>Who can read encrypted messages? Who can read signed ones?</dt>
	224	<dd>Answer coming soon.</dd>
	225
	226	<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>
	227	<dd>Answer coming soon.</dd>
	228	</dl>
	229	</div>
	230	</div>
	231	</section> --><!-- End #faq -->
b592e92f ZR	232
b592e92f ZR	233	<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
1c4bff08 ZR	234	<footer class="row" id="footer">
	235	<div>
	236	<div id="copyright">
	237	<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>
	238	<p>Copyright © 2014-2015 <a href="https://u.fsf.org/ys">Free Software Foundation</a>, Inc. <a href="https://my.fsf.org/donate/privacypolicy.html">Privacy Policy</a>. <a href="https://u.fsf.org/yr">Join.</a></p>
	239	<p><em><a href="http://agpl.fsf.org/emailselfdefense.fsf.org/edward/CURRENT/edward.tar.gz">Source code of Edward reply bot by Josh Drake <zamnedix@gnu.org> available under the GNU General Public License.</a></em></p>
	240	<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>. — <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>
	241	<p>Download the source package for <a href="emailselfdefense_source.zip">this guide</a>. Fonts used in the guide & 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ś, <a href="http://www.google.com/fonts/specimen/Archivo+Narrow">Archivo Narrow</a> by Omnibus-Type, <a href="http://www.thegopherarchive.com/gopher-files-hacks-pxl2000-119351.htm">PXL-2000</a> by Florian Cramer.</p>
	242	<p>
	243	<a href="//weblabels.fsf.org/emailselfdefense.fsf.org/" rel="jslicense">
	244	JavaScript license information
	245	</a>
	246	</p>
	247	</div><!-- /#copyright -->
	248	<p class="credits">
	249	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>
	250	</p><!-- /.credits -->
	251	</div>
	252	</footer><!-- End #footer -->
	253
	254	<script src="http://piwik.fsf.org/piwik.js" async="" defer="" type="text/javascript"></script><script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
9a00aa77	255	<!-- <script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script> -->
b0307a74	256
1c4bff08 ZR	257	<!-- Piwik -->
	258	<script type="text/javascript">
	259	/*
	260	@licstart The following is the entire license notice for the
	261	JavaScript code in this page.
	262
	263	Copyright 2014 Matthieu Aubry
	264
	265	This program is free software: you can redistribute it and/or modify
	266	it under the terms of the GNU General Public License as published by
	267	the Free Software Foundation, either version 3 of the License, or
	268	(at your option) any later version.
	269
	270	This program is distributed in the hope that it will be useful,
	271	but WITHOUT ANY WARRANTY; without even the implied warranty of
	272	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
	273	GNU General Public License for more details.
	274
	275	You should have received a copy of the GNU General Public License
	276	along with this program. If not, see http://www.gnu.org/licenses/.
	277
	278	@licend The above is the entire license notice
	279	for the JavaScript code in this page.
	280	*/
	281	var _paq = _paq \|\| [];
	282	_paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
	283	_paq.push(["setCookieDomain", "*.www.fsf.org"]);
	284	_paq.push(["setDomains", [".www.fsf.org",".www.fsf.org"]]);
	285	_paq.push(["trackPageView"]);
	286	_paq.push(["enableLinkTracking"]);
	287
	288	(function() {
	289	var u=(("https:" == document.location.protocol) ? "https" : "http") + "://piwik.fsf.org/";
	290	_paq.push(["setTrackerUrl", u+"piwik.php"]);
	291	_paq.push(["setSiteId", "5"]);
	292	var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
	293	g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
	294	})();
	295	</script>
	296	<!-- End Piwik Code -->
	297
	298
	299	</body></html>