[enc.git] / sv / 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>
			</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>
				</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 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-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). 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>
				</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="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
d2174714	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	</ul>
	44	<!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
	45	<div id="fsf-intro">
	46	<h3>
	47	<a href="http://u.fsf.org/ys">
	48	<img alt="Free Software Foundation" src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png">
	49	</a>
	50	</h3>
	51	<div class="fsf-emphasis">
	52	<p>
	53	We want to translate this guide
	54	into more languages, and make a version for encryption on mobile
	55	devices. Please donate, and help people around the world take the first
	56	step towards protecting their privacy with free software.
	57	</p>
	58	</div>
	59
	60	<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>
	61
	62	</div><!-- End #fsf-intro -->
	63
	64	<!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
65	<div class="intro">
66	<p>
67	<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>
68	</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>
69
70	</div><!-- End .intro -->
71
72	</div>
73	</header><!-- End #header -->
74
75	<!-- ~~~~~~~~~ Section 1: Get your friends or community interested> ~~~~~~~~~ -->
76	<section style="padding-top: 0px;" class="row" id="section1">
77	<div style="padding-top: 0px;">
78
79	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
80	<div class="section-intro">
81	<p style="margin-top: 0px;" class="image"><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/workshop-section1.png"></p>
82	<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>
83	<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>
84
85	</div><!-- End .section-intro -->
86
87	<div id="step-aa" class="step">
88
89
90	<div class="sidebar">
91	<!-- Workshops image commented out from here, to be used above instead.
92	<p><img id="workshops-image" src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/workshop-section1.png" alt="Workshop icon"></p>-->
93	</div><!-- /.sidebar -->
94
95	<div class="main">
96	<h3>Strength in numbers</h3>
97	<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>
98	</div><!-- End .main -->
99
100	<div class="main">
101	<h3>People you respect may already be using encryption</h3>
102	<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>
103	</div><!-- End .main -->
104
105	<div class="main">
106	<h3>Respect your friends' privacy</h3>
107	<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>
108	</div><!-- End .main -->
109
110
111	<div class="main">
112	<h3>Privacy technology is normal in the physical world</h3>
113	<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>
114	</div><!-- End .main -->
115
116	<div class="main">
117	<h3>We shouldn't have to trust our email providers with our privacy</h3>
118	<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>
119	</div><!-- End .main -->
120
121
122	</div><!-- End #step-2a .step -->
123
124	</div>
125	</section><!-- End #section1 -->
126
127	<!-- ~~~~~~~~~ Section 2: Plan The Workshop ~~~~~~~~~ -->
128	<section class="row" id="section2">
129	<div>
130	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
131	<div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
132	<h2><em>#2</em> Plan The Workshop</h2>
133	<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>
134	</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>
135	<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>
136
137
138	</div><!-- End .section-intro -->
139
140	</div>
141	</section><!-- End #section2 -->
142
143	<!-- ~~~~~~~~~ Section 3: Follow The Guide ~~~~~~~~~ -->
144	<section class="row" id="section3">
145	<div>
146	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
147	<div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
148	<h2><em>#3</em> Follow the guide as a group</h2>
149	<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>
150	<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>
151
152	</div><!-- End .section-intro -->
153	</div>
154	</section>
155
156
157	<!-- ~~~~~~~~~ Section 4: Explain the pitfalls ~~~~~~~~~ -->
158	<section class="row" id="section4">
159	<div>
160	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
161	<div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
162	<h2><em>#4</em> Explain the pitfalls</h2>
163	<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>
164	<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>
165
166
167
168	</div><!-- End .section-intro -->
169
170	</div>
171	</section><!-- End #section4 -->
172
173	<!-- ~~~~~~~~~ Section 5: Explain The Pitfalls ~~~~~~~~~ -->
174	<section id="section5" class="row">
175	<div>
176	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
177	<div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
178	<h2><em>#5</em> Share additional resources</h2>
179	<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>
180
181	</div><!-- End .section-intro -->
182
183
184	</div>
185	</section><!-- End #section5 -->
186
187
188
189	<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
190	<section class="row" id="section6">
191	<div>
192	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
193	<div class="section-intro" style="border: none; padding-bottom: 0px; margin-bottom: 0px;">
194	<h2><em>#6</em> Follow up</h2>
195	<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>
196	<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>
197
198	</div><!-- End .section-intro -->
199
200
201	</div>
202	</section><!-- End #section6 -->
203
204	<!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
205	<!-- When un-commenting this section go to main.css and search
206	for /* Guide Sections Background */ then add #faq to the desired color
207
208	<section class="row" id="faq">
209	<div>
210	<div class="sidebar">
211	<h2>FAQ</h2>
212	</div>
213
214	<div class="main">
215	<dl>
216	<dt>My key expired</dt>
217	<dd>Answer coming soon.</dd>
218
219	<dt>Who can read encrypted messages? Who can read signed ones?</dt>
220	<dd>Answer coming soon.</dd>
221
222	<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>
223	<dd>Answer coming soon.</dd>
224	</dl>
225	</div>
226	</div>
227	</section> --><!-- End #faq -->
228
229	<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
230	<footer class="row" id="footer">
231	<div>
232	<div id="copyright">
233	<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>
234	<p>Copyright © 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>
235
236	<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 <sudoman@ninthfloor.org> and Josh Drake <zamnedix@gnu.org>, available under the GNU Affero General Public License. <a href="http://www.gnu.org/licenses/license-list.html#OtherLicenses">Why these licenses?</a></p>
237
238	<p>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="https://libreplanet.org/wiki/GPG_guide/Graphics_Howto#Pitfalls">PXL-2000</a> by Florian Cramer.</p>
239
240	<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>
241
242	<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>
243	</div><!-- /#copyright -->
244	<p class="credits">
245	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>
246	</p><!-- /.credits -->
247	</div>
248	</footer><!-- End #footer -->
249	<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>
250	<!-- <script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script> -->
251
252	<!-- Piwik -->
253	<script type="text/javascript">
254	/*
255	@licstart The following is the entire license notice for the
256	JavaScript code in this page.
257
258	Copyright 2014 Matthieu Aubry
259
260	This program is free software: you can redistribute it and/or modify
261	it under the terms of the GNU General Public License as published by
262	the Free Software Foundation, either version 3 of the License, or
263	(at your option) any later version.
264
265	This program is distributed in the hope that it will be useful,
266	but WITHOUT ANY WARRANTY; without even the implied warranty of
267	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
268	GNU General Public License for more details.
269
270	You should have received a copy of the GNU General Public License
271	along with this program. If not, see http://www.gnu.org/licenses/.
272
273	@licend The above is the entire license notice
274	for the JavaScript code in this page.
275	*/
276	var _paq = _paq \|\| [];
277	_paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
278	_paq.push(["setCookieDomain", "*.www.fsf.org"]);
279	_paq.push(["setDomains", [".www.fsf.org",".www.fsf.org"]]);
280	_paq.push(["trackPageView"]);
281	_paq.push(["enableLinkTracking"]);
282
283	(function() {
284	var u=(("https:" == document.location.protocol) ? "https" : "http") + "://piwik.fsf.org/";
285	_paq.push(["setTrackerUrl", u+"piwik.php"]);
286	_paq.push(["setSiteId", "5"]);
287	var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
288	g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
289	})();
290	</script>
291	<!-- End Piwik Code -->
292
293
294	</body></html>