<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
<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>
<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
<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>
</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">
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
+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
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>
-
+<script type="text/javascript"
+src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"></script>
+<script type="text/javascript"
+src="//static.fsf.org/nosvn/enc-dev0/js/scripts.js"></script>
<!-- Piwik -->
-<script type="text/javascript" >
-// @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-v3-or-Later
+<script type="text/javascript" ><!--
+// @license magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt GPL-v3-or-Later
var pkBaseURL = (("https:" == document.location.protocol) ? "https://piwik.fsf.org/" : "http://piwik.fsf.org/");
document.write(unescape("%3Cscript src='" + pkBaseURL + "piwik.js' type='text/javascript'%3E%3C/script%3E"));
try {
piwikTracker.enableLinkTracking();
} catch( err ) {}
// @license-end
-</script><noscript><p><img src="//piwik.fsf.org/piwik.php?idsite=13" style="border:0" alt="" /></p></noscript>
+--></script>
+<noscript><p><img
+src="//piwik.fsf.org/piwik.php?idsite=13" style="border:0"
+alt="" /></p></noscript>
<!-- End Piwik Tracking Code -->
-
</body>
</html>
projects / enc.git / commitdiff