From: Adam Leibson Date: Wed, 12 Aug 2015 15:17:57 +0000 (-0400) Subject: commit X-Git-Url: https://vcs.fsf.org/?a=commitdiff_plain;h=c2e62b619388ccb4326b3c80279c56cecb3db86a;p=enc-live.git commit --- diff --git a/en/index.html b/en/index.html index 581c9a5..f93cd80 100644 --- a/en/index.html +++ b/en/index.html @@ -48,7 +48,6 @@
  • Windows
    • -
  • @@ -63,7 +62,6 @@ class="share-logo" alt="[Hacker News]">
    • -
  • V4.0
    • @@ -226,11 +224,11 @@
    Strong Passphrases with Diceware
    Human-made passwords tend to either be very easy to guess, or difficult to memorise and easy to forget. Fortunately, if your privacy is more important to you than an extra 10 to 15 minutes of your time, you can use dice to come up with a password which is both strong and memorable using the 'diceware' method.
    - +
    To use the diceware method, you will need dice (preferably 5, but 1 will do) and this list of words. Do not substitute computer dice for physical dice. Notice that each word on the word list corresponds to a unique five-digit number. Role one dice five times, or five dice once to select the first word. Don't rearrange or discard words, because doing so makes the process much less secure. Repeat this process until you have at least six words, and there's your password.
    Command-line key generation
    -
    If you prefer using the command line for a higher degree of control, you can follow the documentation from the GnuPG Mini Howto or The GNU Privacy Handbook. Make sure you stick with "RSA and RSA" (the default), because it's newer and more secure than algorithms recommended in the old previously mentioned documentation.
    +
    If you prefer using the command line for a higher degree of control, you can follow the documentation from the GnuPG Mini Howto or The GNU Privacy Handbook. Make sure you stick with "RSA and RSA" (the default), because it's newer and more secure than algorithms recommended in the old previously mentioned documentation.
    Advanced key pairs
    When GnuPG creates a new keypair, it compartmentalizes the encryption function from the signing function through subkeys. If you use subkeys carefully, you can keep your GnuPG identity much more secure and recover from a compromised key much more quickly. Alex Cabal and the Debian wiki provide good guides for setting up a secure subkey configuration.
    @@ -345,7 +343,7 @@
    -
    @@ -359,7 +357,7 @@
    ---> + @@ -484,7 +482,7 @@

    Section 5: Use it Well

    -

    Be wary of invalid keys

    +

    Important: Be wary of invalid keys

    GnuPG makes email safer, but it's still important to watch out for invalid keys, which might have fallen into the wrong hands. Email encrypted with invalid keys might be readable by surveillance programs.

    In your email program, go back to the second email that Edward sent you. Because Edward encrypted it with your public key, it will have a message from Enigmail at the top, which most likely says "Enigmail: Part of this message encrypted."

    When using GnuPG, make a habit of glancing at that bar. The program will warn you there if you get an email encrypted with a key that can't be trusted.

    @@ -565,8 +563,8 @@