Changes between Version 8 and Version 9 of MuttGuide/UseGPG


Ignore:
Timestamp:
Oct 21, 2013 7:59:44 PM (4 years ago)
Author:
MichaelRay
Comment:

minor fixes

Legend:

Unmodified
Added
Removed
Modified
  • MuttGuide/UseGPG

    v8 v9  
    4848or you can directly copy and paste it in your muttrc.
    4949
    50 ''NOTE: The pgp_encrypt_only_command and pgp_encrypt_sign_command contain an instruction to also encrypt the message using the author's public key.  That is the option, "--encrypt-to 0xC9C40C31". If you want to automatically encrypt messsages to yourself (for the Sent folder, for example), replace 0xC9C40C31 with your public key's id.  Otherwise, remove the entire --encrypt-to 0xC9C40C31. You will get an error message about not finding the public key if you leave it as-is.''
     50''NOTE: The pgp_encrypt_only_command and pgp_encrypt_sign_command contain an instruction to also encrypt the message using the author's public key.  That is the option, "--encrypt-to 0xC9C40C31". If you want to automatically encrypt messages to yourself (for the Sent folder, for example), replace 0xC9C40C31 with your public key's id.  Otherwise, remove the entire --encrypt-to 0xC9C40C31. You will get an error message about not finding the public key if you leave it as-is.''
    5151
    5252{{{
     
    6767set pgp_sign_as=0x12345678
    6868
    69 # this set the number of seconds to keep in memory the passpharse used to encrypt/sign
     69# this set the number of seconds to keep in memory the passphrase used to encrypt/sign
    7070# the more the less secure it will be
    7171set pgp_timeout=60
     
    144144attack: the more the number of methods you'll use, the less are the
    145145chances that some very determined malicious individual will stole your
    146 identity. Note also that the shared pubblication of your public key
     146identity. Note also that the shared publication of your public key
    147147highly decreases the possibility of your public key be compromised,
    148148since the attacker should compromise <b>at the same time</b> all the
    149149keyservers.
    150150
    151 In case of web pubblication you can attach an header to your outgoing
     151In case of web publication you can attach an header to your outgoing
    152152mail as this:
    153153{{{