[enc.git] / en / workshops.html

<!DOCTYPE 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>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 class="row" id="section1">
			<div>
					<!-- ~~~~~~~~~ section introduction: interspersed text  ~~~~~~~~~ -->
				<div class="section-intro">
						<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="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">
					<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>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">
						<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">
						<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">
						<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">
                                                <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 &copy; 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>. &mdash; <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&#347;, <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="//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
b592e92f ZR	1	<!DOCTYPE html>
	2	<html>
	3	<head>
	4	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
	5
6078cb8e	6	<title>Email Self-Defense - Teach your friends!</title>
b592e92f ZR	7	<meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy, email, Enigmail" />
	8	<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." />
	9
	10	<meta name="viewport" content="width=device-width, initial-scale=1" />
	11	<link rel="stylesheet" href="//static.fsf.org/nosvn/enc-dev0/css/main.css" />
	12	<link rel="shortcut icon" href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />
	13
	14	</head>
	15	<body>
	16
	17	<!-- ~~~~~~~~~ GnuPG Header and introduction text ~~~~~~~~~ -->
	18
	19	<header class="row" id="header">
	20	<div>
b0307a74	21	<h1>Email Self-Defense</h1>
b592e92f	22
77fcfb4a	23	<!-- Languages removed until we have translations-->
b592e92f ZR	24
	25	<ul id="menu" class="os">
	26	<li class="spacer">
a492b0f1	27	<a href="index.html">GNU/Linux</a>
b592e92f ZR	28	</li>
	29	<li>
	30	<a href="mac.html">Mac OS</a>
	31	</li>
	32	<li>
	33	<a href="windows.html">Windows</a>
	34	</li>
10a66c68	35	<li class="spacer"><a href="workshops.html" class="current">Teach your friends</a></li>
b592e92f ZR	36	<li class="spacer">
	37	<a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email encryption for everyone via %40fsf">
	38	Share
	39	<img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png"
	40	class="share-logo" alt="[GNU Social]">
	41	<img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png"
	42	class="share-logo" alt="[Pump.io]">
	43	<img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png"
	44	class="share-logo" alt="[Reddit]">
	45	<img src="//static.fsf.org/nosvn/enc-dev0/img/hacker-news.png"
	46	class="share-logo" alt="[Hacker News]">
	47	</a>
c54f9fc3	48	</li>
b0307a74	49	<li class="spacer">V4.0</li>
b592e92f ZR	50	</ul>
	51	<!-- ~~~~~~~~~ FSF Introduction ~~~~~~~~~ -->
	52	<div id="fsf-intro">
	53	<h3>
	54	<a href="http://u.fsf.org/ys">
119c61ca	55	<img alt="Free Software Foundation" src="//static.fsf.org/nosvn/enc-dev0/img/fsf-logo.png">
b592e92f ZR	56	</a>
	57	</h3>
	58	<div class="fsf-emphasis">
	59	<p>
	60	We fight for computer users'
	61	rights, and promote the development of free (as in freedom) software.
	62	Resisting bulk surveillance is very important to us.
	63	</p>
	64	<p>
	65	<strong>
	66	We want to translate this guide
	67	into more languages, and make a version for encryption on mobile
	68	devices. Please donate, and help people around the world take the first
	69	step towards protecting their privacy with free software.
	70	</strong>
	71	</p>
	72	</div>
	73
119c61ca	74	<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 ZR	75
	76	</div><!-- End #fsf-intro -->
	77
	78	<!-- ~~~~~~~~~ Guide Introduction ~~~~~~~~~ -->
	79	<div class="intro">
	80	<p>
	81	<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>
6078cb8e	82	<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>
b592e92f ZR	83
	84	</div><!-- End .intro -->
	85
	86	</div>
	87	</header><!-- End #header -->
	88
cebc04ac	89	<!-- ~~~~~~~~~ Section 1: Get your friends or community interested> ~~~~~~~~~ -->
b592e92f ZR	90	<section class="row" id="section1">
	91	<div>
	92	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	93	<div class="section-intro">
cebc04ac	94	<h2><em>#1</em> Get your friends or community interested </h2>
e64d9809	95	<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>
9fcfafe0	96	<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>
b592e92f ZR	97
b592e92f ZR	98	</div><!-- End .section-intro -->
c8a179b6 AL	99
	100	<div id="step-aa" class="step">
	101	<div class="main">
d4a7d4c9	102	<h3>Strength in numbers</h3>
9fcfafe0	103	<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>
c8a179b6	104	</div><!-- End .main -->
d4a7d4c9	105
9fcfafe0 ZR	106	<div class="main">
	107	<h3>People you respect may already be using encryption</h3>
	108	<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>
	109	</div><!-- End .main -->
	110
d4a7d4c9 AL	111	<div class="main">
	112	<h3>Respect your friends' privacy</h3>
	113	<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>
	114	</div><!-- End .main -->
	115
	116
	117	<div class="main">
	118	<h3>Privacy technology is normal in the physical world</h3>
	119	<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>
	120	</div><!-- End .main -->
	121
	122
c8a179b6 AL	123	</div><!-- End #step-2a .step -->
c8a179b6 AL	124
b592e92f	125	</div>
c8a179b6	126	</section><!-- End #section1 -->
b592e92f	127
2a2efbd7	128	<!-- ~~~~~~~~~ Section 2: Plan The Workshop ~~~~~~~~~ -->
b592e92f ZR	129	<section class="row" id="section2">
	130	<div>
	131	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	132	<div class="section-intro">
2a2efbd7	133	<h2><em>#2</em> Plan The Workshop</h2>
e64d9809	134	<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>
2a2efbd7 AL	135	<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>
2a2efbd7 AL	136	<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	137
b592e92f	138
b592e92f ZR	139	</div><!-- End .section-intro -->
b592e92f ZR	140
b592e92f ZR	141	</div>
	142	</section><!-- End #section2 -->
	143
f639bad8	144	<!-- ~~~~~~~~~ Section 3: Follow The Guide ~~~~~~~~~ -->
b592e92f ZR	145	<section class="row" id="section3">
	146	<div>
	147	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	148	<div class="section-intro">
f639bad8 AL	149	<h2><em>#3</em> Follow the guide as a group</h2>
	150	<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>
	151	<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>
e64d9809	152	<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 ZR	153
b592e92f ZR	154	</div><!-- End .section-intro -->
b592e92f	155	</div>
f639bad8	156	</section>
b592e92f ZR	157
b592e92f ZR	158
c907f9f1	159	<!-- ~~~~~~~~~ Section 4: Explain the pitfalls ~~~~~~~~~ -->
b592e92f ZR	160	<section class="row" id="section4">
	161	<div>
	162	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	163	<div class="section-intro">
c907f9f1	164	<h2><em>#4</em> Explain the pitfalls</h2>
12727276	165	<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>
c907f9f1	166	<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 ZR	167
	168
	169
	170	</div><!-- End .section-intro -->
	171
b592e92f ZR	172	</div>
	173	</section><!-- End #section4 -->
	174
fa8bc9da	175	<!-- ~~~~~~~~~ Section 5: Explain The Pitfalls ~~~~~~~~~ -->
b592e92f ZR	176	<section id="section5" class="row">
	177	<div>
	178	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	179	<div class="section-intro">
6caadc0a	180	<h2><em>#5</em> Share additional resources</h2>
bb0ef9bb	181	<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	182
b592e92f ZR	183	</div><!-- End .section-intro -->
	184
	185
	186	</div>
	187	</section><!-- End #section5 -->
	188
	189
	190
	191	<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
	192	<section class="row" id="section6">
da96bef7 AL	193	<div>
	194	<!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
	195	<div class="section-intro">
87bb4a1e AL	196	<h2><em>#6</em> Follow up</h2>
	197	<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>
	198	<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	199
da96bef7	200	</div><!-- End .section-intro -->
b592e92f	201
da96bef7 AL	202
da96bef7 AL	203	</div>
b592e92f ZR	204	</section><!-- End #section6 -->
	205
	206	<!-- ~~~~~~~~~ FAQ ~~~~~~~~~ -->
	207	<!-- When un-commenting this section go to main.css and search
	208	for /* Guide Sections Background */ then add #faq to the desired color
	209
	210	<section class="row" id="faq">
	211	<div>
	212	<div class="sidebar">
	213	<h2>FAQ</h2>
	214	</div>
	215
	216	<div class="main">
	217	<dl>
	218	<dt>My key expired</dt>
	219	<dd>Answer coming soon.</dd>
	220
	221	<dt>Who can read encrypted messages? Who can read signed ones?</dt>
	222	<dd>Answer coming soon.</dd>
	223
	224	<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>
	225	<dd>Answer coming soon.</dd>
	226	</dl>
	227	</div>
	228	</div>
	229	</section> --><!-- End #faq -->
	230
	231	<!-- ~~~~~~~~~ Footer ~~~~~~~~~ -->
	232	<footer class="row" id="footer">
	233	<div>
	234	<div id="copyright">
8f2f9359	235	<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>
866845c9	236	<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>
8f2f9359 ZR	237	<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>
	238	<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>
	239	<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>
b592e92f	240	<p>
8f2f9359 ZR	241	<a href="//weblabels.fsf.org/emailselfdefense.fsf.org/"
8f2f9359 ZR	242	rel="jslicense">
b592e92f ZR	243	JavaScript license information
	244	</a>
	245	</p>
	246	</div><!-- /#copyright -->
	247	<p class="credits">
8f2f9359	248	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>
b592e92f ZR	249	</p><!-- /.credits -->
	250	</div>
	251	</footer><!-- End #footer -->
	252
b0307a74 ZR	253	<script src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
	254	<script src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
	255
b592e92f ZR	256	<!-- Piwik -->
	257	<script type="text/javascript">
	258	/*
	259	@licstart The following is the entire license notice for the
	260	JavaScript code in this page.
	261
	262	Copyright 2014 Matthieu Aubry
	263
	264	This program is free software: you can redistribute it and/or modify
	265	it under the terms of the GNU General Public License as published by
	266	the Free Software Foundation, either version 3 of the License, or
	267	(at your option) any later version.
	268
	269	This program is distributed in the hope that it will be useful,
	270	but WITHOUT ANY WARRANTY; without even the implied warranty of
	271	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
	272	GNU General Public License for more details.
	273
	274	You should have received a copy of the GNU General Public License
	275	along with this program. If not, see http://www.gnu.org/licenses/.
	276
	277	@licend The above is the entire license notice
	278	for the JavaScript code in this page.
	279	*/
	280	var _paq = _paq \|\| [];
	281	_paq.push(["setDocumentTitle", document.domain + "/" + document.title]);
	282	_paq.push(["setCookieDomain", "*.www.fsf.org"]);
	283	_paq.push(["setDomains", [".www.fsf.org",".www.fsf.org"]]);
	284	_paq.push(["trackPageView"]);
	285	_paq.push(["enableLinkTracking"]);
	286
	287	(function() {
	288	var u=(("https:" == document.location.protocol) ? "https" : "http") + "://piwik.fsf.org/";
	289	_paq.push(["setTrackerUrl", u+"piwik.php"]);
	290	_paq.push(["setSiteId", "5"]);
	291	var d=document, g=d.createElement("script"), s=d.getElementsByTagName("script")[0]; g.type="text/javascript";
	292	g.defer=true; g.async=true; g.src=u+"piwik.js"; s.parentNode.insertBefore(g,s);
	293	})();
	294	</script>
	295	<!-- End Piwik Code -->
8f2f9359 ZR	296	</body>
8f2f9359 ZR	297	</html>