X-Git-Url: https://vcs.fsf.org/?a=blobdiff_plain;f=en%2Findex.html;h=d3e2c5d53d9be1a24ef62a148000401ae022616f;hb=a3a9a0acf3552b45e59872c6067832c26b83e22d;hp=8c91024cdf6631403974f287c25f66131dcd233b;hpb=799d528d3c6ec8009f5c678fcd6157b8eda56f29;p=enc-live.git diff --git a/en/index.html b/en/index.html index 8c91024..d3e2c5d 100644 --- a/en/index.html +++ b/en/index.html @@ -15,7 +15,11 @@ self-defense in 40 minutes with GnuPG." /> href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" /> - + + + + +

@@ -25,8 +29,8 @@ href="//static.fsf.org/nosvn/enc-dev0/img/favicon.ico" />

Note: As of June 18, 2018, GnuPG 2.2.8 is unavailable for Debian stable and -testing.

@@ -279,7 +281,7 @@ look up your public key.

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. You should never share you private key with anyone, under any +bold;">You should never share your private key with anyone, under any circumstances.

In addition to encryption and decryption, you can also use these keys to @@ -321,7 +323,7 @@ key pair for signing and encrypting my email."

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 this article by Micah Lee.

@@ -362,17 +364,10 @@ Tools. for GnuPG, then install it. Then restart the Enigmail setup wizard by going to Enigmail → Setup Wizard. -

My email looks weird

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.

More resources

If you're having trouble with our instructions or just want to learn more, check out +href="https://www.enigmail.net/documentation/Key_Management#Generating_your_own_key_pair"> Enigmail's wiki instructions for key generation.

Don't see a solution to your problem?

@@ -421,8 +416,10 @@ provide good guides for setting up a secure subkey configuration.

In your email program's menu, select Enigmail → Key Management.

Right click on your key and select Upload Public Keys to Keyserver. Use -the default keyserver in the popup.

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.

Now someone who wants to send you an encrypted message can download your public key from the Internet. There are multiple keyservers @@ -447,7 +444,7 @@ keyserver.

Step 3.c Receive a response

When Edward receives your email, he will use his private key to decrypt -it, then use your public key (which you sent him in Step -3.A) to encrypt his reply to you.

+it, then reply to you.

It may take two or three minutes for Edward to respond. In the meantime, you might want to skip ahead and check out the Use it Well section of this guide.

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.

- -

Notice the bar that Enigmail shows you above the message, with information -about the status of Edward's key.

@@ -713,9 +702,9 @@ be encrypted, signed, both, or neither.

Step 3.e Receive a response

When Edward receives your email, he will use your public key (which you -sent him in Step 3.A) to verify that your signature -is authentic and the message you sent has not been tampered with.

When Edward receives your email, he will use your public key (which +you sent him in Step 3.A) to verify the message +you sent has not been tampered with and to encrypt his reply to you.

It may take two or three minutes for Edward to respond. In the meantime, you might want to skip ahead and check out the +

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.

+ +

Notice the bar that Enigmail shows you above the message, with +information about the status of Edward's key.

+ @@ -999,7 +995,7 @@ of your new key.

Transferring you key

You can use Enigmail's key management +href="https://www.enigmail.net/documentation/Key_Management">key management window 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 Creative Commons Attribution-ShareAlike 4.0 license (or later version). Download the source code of Edward reply bot 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. Why these licenses?

@@ -1144,20 +1140,24 @@ src="//static.fsf.org/nosvn/enc-dev0/js/jquery-1.11.0.min.js"> - - - + + + + +