--- /dev/null
+<!DOCTYPE html>
+<html>
+ <head>
+ <meta http-equiv="content-type" content="text/html; charset=utf-8" />
+
+ <title>Email Self-Defense - a guide to fighting surveillance with GnuPG encryption</title>
+ <meta name="keywords" content="GnuPG, GPG, openpgp, surveillance, privacy, email, Enigmail" />
+ <meta name="description" content="Email surveillance violates our fundamental rights and makes free speech risky. This guide will teach you email self-defense in 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>Teach an Email Self-Defense Workshop</h1>
+
+ <!-- Language list for browsers that do not have JS enabled -->
+ <ul id="languages" class="os">
+ <li><a class="current" href="/en">english</a></li>
+ <li><a href="/es">español</a></li>
+ <li><a href="/fr">français</a></li>
+ <li><a href="/de">deutsch</a></li>
+ <li><a href="/it">italiano</a></li>
+ <li><a href="/pt-br">português do Brasil</a></li>
+ <li><a href="/tr">türkçe</a></li>
+ <li><a href="/ro">română</a></li>
+ <li><a href="/ru">русский</a></li>
+ <!--<li><a href="/ml">മലയാളം</a></li>-->
+ <!--<li><a href="/ko">한국어</a></li>-->
+ <li><a href="/ja">日本語</a></li>
+ <li><a href="/el">ελληνικά</a></li>
+ <!--<li><a href="/ar">العربية</a></li>-->
+ </ul>
+
+ <ul id="menu" class="os">
+ <li class="spacer">
+ <a href="index.html">GNU/Linux</a>
+ </li>
+ <li>
+ <a href="mac.html">Mac OS</a>
+ </li>
+ <li>
+ <a href="windows.html">Windows</a>
+ </li>
+<li class="spacer"><a href="workshops.html" class="current">Lead a workshop</a></li>
+ <li class="spacer">
+ <a href="https://fsf.org/share?u=https://u.fsf.org/zb&t=Email encryption for everyone via %40fsf">
+ Share
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/gnu-social.png"
+ class="share-logo" alt="[GNU Social]">
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/pump.io.png"
+ class="share-logo" alt="[Pump.io]">
+ <img src="//static.fsf.org/nosvn/enc-dev0/img/reddit-alien.png"
+ class="share-logo" alt="[Reddit]">
+ <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="Email%20Self-Defense%20-%20a%20guide%20to%20fighting%20surveillance%20with%20GnuPG%20encryption_files/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&id=14&pk_campaign=email_self_defense&pk_kwd=guide_donate"><img alt="Donate" src="Email%20Self-Defense%20-%20a%20guide%20to%20fighting%20surveillance%20with%20GnuPG%20encryption_files/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 & share our infographic →"></a>
+ Each person who chooses to resist mass surveillance makes it easier and less out of the ordinary for others to resist as well. People normalizing the use of strong cryptography helps whistle-blowers, dissidents, and activists and blend in better by providing cover traffic.</p>
+
+<p>There's no objective method of what constitutes an interesting correspondance. As such, don't presume just because you find an email you sent to a friend innocous, your friend (or a third party, for that matter!) feels the same way. Show your friends respect by encrypting your correspondences with them.</p>
+
+<p>Without our collective complacency, mass surveillance loses its effectiveness. This guide aims to help you facilitate Email Self-Defense workshops within your community, so that we may all stand a better chance of making the world a better, freer place!</p>
+
+ </div><!-- End .intro -->
+
+ </div>
+ </header><!-- End #header -->
+
+<!-- ~~~~~~~~~ Section 0: Why GnuPG> ~~~~~~~~~ -->
+ <section class="row" id="section1">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#0</em> Why GnuPG? </h2>
+
+<p>NSA whistleblower Edward Snowden once famously <a href="http://www.theguardian.com/world/2013/jun/17/edward-snowden-nsa-files-whistleblower?CMP=twt_gu#block-51bf3588e4b082a2ed2f5fc5">wrote </a>, "Encryption works." When he chose to leak his information <a href="https://firstlook.org/theintercept/2014/10/28/smuggling-snowden-secrets/"> to film maker Laura Poitras</a>, he put his trust in the GNU Privacy Guard , and it didn't let him down. Although “encryption works,” even the most perfect software and algorithms still fail when the underlying system is not secure, or if the user doesn't understand how to properly make the software work for them.</p>
+
+<p>Setting up a secure computer and understanding how it works is a daunting task, even for many advanced users. Simple mistakes lead to disaster, and many people who would benefit from using GnuPG don't simply because the process sounds too complex. GnuPG is a powerful and versatile program, and it's sad that more people don't use it.</P>
+
+<p>If you already love GnuPG, do your part to help increase herd immunity to mass surveillance by helping your friends and neighbors master the challenges GnuPG poses. Help them keep their digital love letters private, and teach them the benefits of free software. Oftentimes, users over-calculate the complexity of setting up GnuPG, when all they really need is a ally to sit down with them and help them get started. Go be that friend!</P>
+
+<p>To fully benefit from this guide, please read it in its entirety before proceeding.</p>
+
+ </div><!-- End .section-intro -->
+ </div>
+ </section><!-- End #section0 -->
+
+<!-- ~~~~~~~~~ Section 1: Plan The Workshop ~~~~~~~~~ -->
+ <section class="row" id="section2">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#1</em> Plan The Workshop</h2>
+ <p>When you hear friends bemoaning their lack of digital privacy, ask them if they're interested in attending a workshop to on email self-defense. Once you've got a handful of people interested, pick a date and start planning out the event. Tell participants to bring their computer, their ID (for signing each other's key) and a flash drive.</p>
+
+<p>The success of each workshop requires understanding and catering to the unique background and needs of each group of participants. Workshops should stay small, so that participants receive more individualized instruction. If more than a handful of people want to participate, keep the participant:facilitator ratio low by recruiting more facilitators, or by facilitating multiple workshops. Ideally, facilitators should be known and trusted members of the participants' community. Small workshops among friends work great!</p>
+
+<p>Many activists, journalists, whistleblowers, businessfolk, academics, and dissidents use the OpenPGP standard, so participants might unknowingly know of a few people who use it already. If possible, make a list of people and organizations that use OpenPGP which participants will likely recognize by searching for <a href="https://duckduckgo.com/?q=%22BEGIN+PGP+PUBLIC+KEY+BLOCK%22+%2B+%22free+software%22">"BEGIN PGP PUBLIC KEY BLOCK" + keyword</a>.</p>
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-1a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step1a-install-wizard.png" alt="Step 2.A: Make a Keypair"></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 1.a</em> Space and Preparation</h3>
+ <p>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. Try and get all the participants to set up an Enigmail-compatible email client before the event. Direct them to their organizations IT department or help page if they run into errors. Estimate that the workshop to take at a minimum 30 minutes plus about five to 10 minutes for each participant. Plan extra time for glitches and questions.</p>
+
+ </div><!-- End .main -->
+ </div><!-- End #terminology.step-->
+
+
+ </div>
+ </section><!-- End #section2 -->
+
+<!-- ~~~~~~~~~ Section 2: Follow The Guide ~~~~~~~~~ -->
+ <section class="row" id="section3">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#2</em> Follow The Guide</h2>
+ <p>Have the participants work through the Email Self-Defense guide a step at a time on their own computers. Make sure all participants complete each step before the group moves on to the next step. Talk about each step, but be sure not to overload the participants with minutia. Pitch the bulk of your instruction to the least tech-savvy participants. Consider holding a secondary workshop afterwards for the outliers in either direction.</p>
+
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-2a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/step2a-01-make-keypair.png" alt="Try it out."></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 2.a</em> Public and Private Keys key</h3>
+ <p>Make sure all the participants have a conceptual understanding of the relationship between public and private keys in a keypair. It's normal for people to not understand public-key cryptography on the first try. Use analogies to help explain the concept.</p>
+
+ </div><!-- End .main -->
+ </div><!-- End #step-2a .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-2b" class="step">
+<div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section5-02-use-it-well.png" alt="Section 5: Use it Well" /></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 2.b</em> Diceware and Passphrases</h3>
+ <p>Sufficiently strong passphrases <a href="https://firstlook.org/theintercept/2015/03/26/passphrases-can-memorize-attackers-cant-guess/"> can't easily be brute forced</a>, and thus protect the private key even if it falls into the wrong hands. Recommend participants use the <a href="http://world.std.com/~reinhold/diceware.html"> diceware method </a>, and have dice and the wordlist available for them to use. Participants who choose to use diceware should keep their passphrase with them at all at all times until they memorize it. Stress the importance of creating and backing up revocation certificates, especially to participants who write down their diceware passphrases.</p>
+ <!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
+ <div class="troubleshooting">
+ <h4>Disclaimer</h4>
+ <dl>
+ <dt>Diceware and Licensing</dt>
+ <dd>Something here about diceware's relationship with free software, or something.</dd>
+ </dl>
+ </div><!-- /.troubleshooting -->
+
+ </div><!-- End .main -->
+ </div><!-- End #step-3b .step -->
+
+
+ </div>
+ </section><!-- End #section3 -->
+
+
+<!-- ~~~~~~~~~ Section 3: Sign Keys ~~~~~~~~~ -->
+ <section class="row" id="section4">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#3</em> Sign Keys</h2>
+ <p>Emphasize the distinction between trusting a person subjectively, and seeing whose keys they've signed objectively. Without a proper understanding of trust, the beautiful transative trust properties of the web of trust are lost. Since trust is an internal and subjective thing, it's unnecessary for participants to share how much they trust another participant with anyone else.</p>
+
+<p>Have the participants download each other's keys, read out their own fingerprints, and present their IDs to each other. Help participants navigate the interface to sign each other's keys, and encourage participants to assign each other trust levels if they already know each other.</p>
+
+
+
+ </div><!-- End .section-intro -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-4a" class="step">
+ <div class="sidebar">
+ <p><img src="//static.fsf.org/nosvn/enc-dev0/img/en/screenshots/section4-web-of-trust.png" alt="Section 4: Web of Trust"></p>
+ </div><!-- /.sidebar -->
+ <div class="main">
+ <h3><em>Step 4.a</em> Sign a key</h3>
+ <p>In your email program's menu, go to Enigmail → Key Management.</p>
+ <p>Right click on Edward's public key and select Sign Key from the context menu.</p>
+ <p>In the window that pops up, select "I will not answer" and click ok.</p>
+ <p>Now you should be back at the Key Management menu. Select Keyserver → Upload Public Keys and hit ok.</p>
+ <p class="notes">You've just effectively said "I trust that
+Edward's public key actually belongs to Edward." This doesn't mean much
+because Edward isn't a real person, but it's good practice.</p>
+
+
+ <!--<div id="pgp-pathfinder">
+ <form enctype="application/x-www-form-urlencoded" action="/mk_path.cgi" method="get">
+ <p><strong>From:</strong> <input type="text" placeholder="xD41A008" name="FROM"></p>
+ <p><strong>To:</strong> <input type="text" placeholder="50BD01x4" name="TO"></p>
+ <p class="buttons"><input type="submit" value="trust paths" name="PATHS"> <input type="reset" value="reset" name=".reset"></p>
+ </form>
+ </div><!-- End #pgp-pathfinder -->
+
+ </div><!-- End .main -->
+ </div><!-- End #step-4a .step -->
+
+ <!-- ~~~~~~~~~ a div for each step ~~~~~~~~~ -->
+ <div id="step-sign_real_keys" class="step">
+ <div class="main">
+ <h3><em>Important:</em> check people's identification before signing their keys</h3>
+ <p>Before signing a real person's key, always make sure it
+actually belongs to them, and that they are who they say they are. Ask
+them to show you their ID (unless you trust them very highly) and their
+public key fingerprint -- not just the shorter public key ID, which
+could refer to another key as well. In Enigmail, answer honestly in the
+window that pops up and asks "How carefully have you verified that the
+key you are about to sign actually belongs to the person(s) named
+above?".</p>
+ </div><!-- End .main -->
+ </div><!-- End #step-sign_real_keys .step-->
+
+
+
+ </div>
+ </section><!-- End #section4 -->
+
+<!-- ~~~~~~~~~ Section 4: Explain The Pitfalls ~~~~~~~~~ -->
+ <section id="section5" class="row">
+ <div>
+ <!-- ~~~~~~~~~ section introduction: interspersed text ~~~~~~~~~ -->
+ <div class="section-intro">
+ <h2><em>#4</em> Explain the pitfalls</h2>
+<p>Remind participants that encryption works only where it's explicitly used; they won't be able to send an encrypted email to someone who hasn't set up encrption already. Also remind them to make sure encryption is selected before hitting send. Explain metadata to the participants, and advise them to use bland-sounding subject lines.</p>
+
+<p>Advocate for free software, for without it, we can't meaningfully resist invasions of our digital privacy and autonomy. Explain the <a href="http://www.gnu.org/philosophy/proprietary-surveillance.html">dangers</a> of running a proprietary system, and why GnuPG can't begin to mitigate them.</p>
+ </div><!-- End .section-intro -->
+
+
+ </div>
+ </section><!-- End #section5 -->
+
+
+
+<!-- ~~~~~~~~~ Section 6: Next steps ~~~~~~~~~ -->
+ <section class="row" id="section6">
+ <div id="step-click_here" class="step">
+ <div class="main">
+ <h2><a href="https://emailselfdefense.fsf.org/en/next_steps.html">Great job! Check out the next steps.</a></h2>
+
+ </div><!-- End .main -->
+ </div><!-- End #step-click_here .step-->
+
+ </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="Email%20Self-Defense%20-%20a%20guide%20to%20fighting%20surveillance%20with%20GnuPG%20encryption_files/fsf-logo.png"></a></h4>
+ <p>Copyright © 2014 <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>Version 3.0. <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>
+<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="https://emailselfdefense.fsf.org/en/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>
+ <p>
+ <a href="https://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="Email%20Self-Defense%20-%20a%20guide%20to%20fighting%20surveillance%20with%20GnuPG%20encryption_files/jplusplus.png" alt="Journalism++"></a>
+ </p><!-- /.credits -->
+ </div>
+ </footer><!-- End #footer -->
+
+ <script src="Email%20Self-Defense%20-%20a%20guide%20to%20fighting%20surveillance%20with%20GnuPG%20encryption_files/piwik.js" async="" defer="defer" type="text/javascript"></script><script src="Email%20Self-Defense%20-%20a%20guide%20to%20fighting%20surveillance%20with%20GnuPG%20encryption_files/jquery-1.js"></script>
+ <script src="Email%20Self-Defense%20-%20a%20guide%20to%20fighting%20surveillance%20with%20GnuPG%20encryption_files/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>
projects / enc.git / commitdiff