<ul id="languages" class="os">
<li><a class="current" href="/en">English - v4.0</a></li>
<li><a href="/ar">العربية <span class="tip">tip</span></a></li>
-<li><a href="/cs">Ä\8ceština - v4.0</a></li>
-<li><a href="/de">Deutsch - v3.0</a></li>
+<li><a href="/cs">Ä\8deština - v4.0</a></li>
+<li><a href="/de">Deutsch - v4.0</a></li>
<li><a href="/el">ελληνικά - v3.0</a></li>
<li><a href="/es">español - v4.0</a></li>
<li><a href="/fa">فارسی - v4.0</a></li>
<li><a href="/sq">Shqip - v4.0</a></li>
<li><a href="/sv">svenska - v4.0</a></li>
<li><a href="/tr">Türkçe - v4.0</a></li>
-<li><a href="/zh-hans">简体中文 <span class="tip">tip</span></a></li>
-<li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide"><strong><span
-style="color: #2F5FAA;">Translate!</span></strong></a></li>
+<li><a href="/zh-hans">简体中文 - v4.0</a></li>
+<li><a href="https://libreplanet.org/wiki/GPG_guide/Translation_Guide">
+<strong><span style="color: #2F5FAA;">Translate!</span></strong></a></li>
</ul>
<ul id="menu" class="os">
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/mastodon.png" class="share-logo"
+alt="[Mastodon]" />
<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"
<p>Your private key is more like a physical key, because you keep it to
yourself (on your computer). You use GnuPG and your private key together to
descramble encrypted emails other people send to you. <span style="font-weight:
-bold;">You should never share you private key with anyone, under any
+bold;">You should never share your private key with anyone, under any
circumstances.</span></p>
<p>In addition to encryption and decryption, you can also use these keys to
<li>On the screen titled "Create Key," pick a strong password! You can
do it manually, or you can use the Diceware method. Doing it manually
is faster but not as secure. Using Diceware takes longer and requires
-dice, but creates a password that is much harder for attackers figure
+dice, but creates a password that is much harder for attackers to figure
out. To use it, read the section "Make a secure passphrase with Diceware" in <a
href="https://theintercept.com/2015/03/26/passphrases-can-memorize-attackers-cant-guess/">
this article</a> by Micah Lee.</li>
of three stacked horizontal bars. Enigmail may be inside a section called
Tools.</dd>
-<dt>The wizard says that it cannot find GnuPG.</dt>
-<dd>Open whatever program you usually use for installing software, and search
-for GnuPG, then install it. Then restart the Enigmail setup wizard by going
-to Enigmail → Setup Wizard.</dd>
-
-<dt>My email looks weird</dt>
-<dd>Enigmail doesn't tend to play nice with HTML, which is used to format
-emails, so it may disable your HTML formatting automatically. To send an
-HTML-formatted email without encryption or a signature, hold down the Shift
-key when you select compose. You can then write an email as if Enigmail
-wasn't there.</dd>
-
<dt>More resources</dt>
<dd>If you're having trouble with our
instructions or just want to learn more, check out <a
-href="https://enigmail.wiki/Key_Management#Generating_your_own_key_pair">
+href="https://www.enigmail.net/documentation/Key_Management#Generating_your_own_key_pair">
Enigmail's wiki instructions for key generation</a>.</dd>
<dt class="feedback">Don't see a solution to your problem?</dt>
<p>In your email program's menu, select Enigmail → Key Management.</p>
-<p>Right click on your key and select Upload Public Keys to Keyserver. Use
-the default keyserver in the popup.</p>
+<p>Right click on your key and select Upload Public Keys to Keyserver. You
+don't have to use the default keyserver. If, after research, you would like
+to change to a different default keyserver, you can change that setting
+manually in the Enigmail preferences.</p>
<p class="notes">Now someone who wants to send you an encrypted message can
download your public key from the Internet. There are multiple keyservers
<dt>More documentation</dt>
<dd>If you're having trouble with our
instructions or just want to learn more, check out <a
-href="https://www.enigmail.net/documentation/quickstart-ch2.php#id2533620">
+href="https://www.enigmail.net/documentation/Key_Management#Distributing_your_public_key">
Enigmail's documentation</a>.</dd>
<dt class="feedback">Don't see a solution to your problem?</dt>
<dt>More resources</dt>
<dd>If you're still having trouble with our
instructions or just want to learn more, check out <a
-href="https://enigmail.wiki/Signature_and_Encryption#Encrypting_a_message">
+href="https://www.enigmail.net/documentation/Signature_and_Encryption#Encrypting_a_message">
Enigmail's wiki</a>.</dd>
<dt class="feedback">Don't see a solution to your problem?</dt>
<h3><em>Step 3.c</em> Receive a response</h3>
<p>When Edward receives your email, he will use his private key to decrypt
-it, then use your public key (which you sent him in <a href="#step-3a">Step
-3.A</a>) to encrypt his reply to you.</p>
+it, then reply to you. </p>
<p class="notes">It may take two or three minutes for Edward to
respond. In the meantime, you might want to skip ahead and check out the <a
href="#section5">Use it Well</a> section of this guide.</p>
-<p>When you receive Edward's email and open it, Enigmail will automatically
-detect that it is encrypted with your public key, and then it will use your
-private key to decrypt it.</p>
-
-<p>Notice the bar that Enigmail shows you above the message, with information
-about the status of Edward's key.</p>
-
</div><!-- End .main -->
</div><!-- End #step-3c .step -->
<h3><em>Step 3.e</em> Receive a response</h3>
-<p>When Edward receives your email, he will use your public key (which you
-sent him in <a href="#step-3a">Step 3.A</a>) to verify that your signature
-is authentic and the message you sent has not been tampered with.</p>
+<p>When Edward receives your email, he will use your public key (which
+you sent him in <a href="#step-3a">Step 3.A</a>) to verify the message
+you sent has not been tampered with and to encrypt his reply to you.</p>
<p class="notes">It may take two or three minutes for Edward to
respond. In the meantime, you might want to skip ahead and check out the <a
"Your signature was verified." If your test signed email was also encrypted,
he will mention that first.</p>
+<p>When you receive Edward's email and open it, Enigmail will
+automatically detect that it is encrypted with your public key, and
+then it will use your private key to decrypt it.</p>
+
+<p>Notice the bar that Enigmail shows you above the message, with
+information about the status of Edward's key.</p>
+
</div><!-- End .main -->
</div><!-- End #step-3e .step -->
</div></section>
<h3>Transferring you key</h3>
<p>You can use Enigmail's <a
-href="https://www.enigmail.net/documentation/keyman.php">key management
+href="https://www.enigmail.net/documentation/Key_Management">key management
window</a> to import and export keys. If you want to be able to read
your encrypted email on a different computer, you will need to export
your secret key from here. Be warned, if you transfer the key without <a
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>,
+<andrew@engelbrecht.io> 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>