<div class="main">
<h3><em>Step 3.b</em> Send a test encrypted email</h3>
<p>Write a new email in your email program, addressed to edward-en@fsf.org. Make the subject "Encryption test" or something similar and write something in the body.</p>
- <p>The key in the bottom right of the window should be yellow, meaning encryption is on. This will be your default from now on.</p>
+ <p>The key in the top left of the window should be yellow, meaning encryption is on. This will be your default from now on.</p>
<p class="notes">Next to the key, you'll notice an icon of a pencil. We'll get to this in a moment.</p>
<p>Click Send. Enigmail will pop up a window that says "Recipients not valid, not trusted or not found."</p>
<p>Now you are back at the "Recipients not valid, not trusted or not found" screen. Check the box in front of Edward's key and click Send.</p>
-<p class="notes">Since you encrypted this email with Edward's public key, Edward's private key is required to decrypt it. Edward is the only one with his private key, so no one except him can decrypt it. Even you can't decrypt it, but your email program will automatically save a copy encrypted with your public key instead of Edwards, which you'll be able to view from the Sent folder like a normal email.</p>
+<p class="notes">Since you encrypted this email with Edward's public key, Edward's private key is required to decrypt it. Edward is the only one with his private key, so no one except him can decrypt it.</p>
<!-- ~~~~~~~~~ Troubleshooting ~~~~~~~~~ -->
<div class="troubleshooting">
<h4>Troubleshooting</h4>
<dl>
<dt>Enigmail can't find Edward's key</dt>
<dd>Close the pop-ups that have appeared since you clicked Send. Make sure you are connected to the Internet and try again. If that doesn't work, repeat the process, choosing a different keyserver when it asks you to pick one.</dd>
+ <dt>Unscrambled messages in Sent folder</dt>
+ <dd>Even though you can't decrypt messages encrypted to someone else's key, your email program will automatically save a copy encrypted to your public key, which you'll be able to view from the Sent folder like a normal email. This is normal, and it is not a cause for alarm.</dd>
<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">Enigmail's wiki</a>.</dd>
<dt class="feedback">Don't see a solution to your problem?</dt>
<dl>
<dt>Master the Web of Trust</dt>
<dd>Unfortunately, trust does not spread between users the way <a href="http://fennetic.net/irc/finney.org/~hal/web_of_trust.html">many people think</a>. One of best ways to strengthen the GnuPG community is to properly <a href="https://www.gnupg.org/gph/en/manual/x334.html">understand</a> the web of trust and to carefully sign as many people's keys as <a href="http://www.cryptnet.net/fdp/crypto/keysigning_party/en/keysigning_party.html">circumstances</a> permit.</dd>
+ <dt>Set ownertrust</dt>
+ <dd>If you trust someone enough to validate other people's keys, you can assign them an ownertrust level through Enigmails's key management window. Right click on the other person's key, go to the 'Select Owner Trust' menu option, select the trustlevel and click OK. Only do this if you fully understand the implications.</dd>
</dl>
</div><!-- /.troubleshooting -->
</div><!-- End .main -->
projects / enc.git / commitdiff