Changes between Version 3 and Version 4 of MuttFaq/Encryption


Ignore:
Timestamp:
Oct 27, 2013 12:55:29 PM (4 years ago)
Author:
MichaelRay
Comment:

minor fixes to wikiml and a little grammer/style

Legend:

Unmodified
Added
Removed
Modified
  • MuttFaq/Encryption

    v3 v4  
    1515
    1616* With recent Mutts >= 1.5.7, use the '''<check-traditional-pgp>''' function automatically inside a '''message-hook''', setting this one line in muttrc:
    17 <pre><nowiki>  message-hook '!(~g|~G) ~b"^-----BEGIN\ PGP\ (SIGNED\ )?MESSAGE"' "exec check-traditional-pgp"</nowiki></pre>
     17{{{
     18  message-hook '!(~g|~G) ~b"^-----BEGIN\ PGP\ (SIGNED\ )?MESSAGE"' "exec check-traditional-pgp"
     19}}}
    1820: '''Note:''' This doesn't work so well with inline signatures within MIME digests.
    1921* Use the '''pgp_auto_decode''' option, which is very similar to the message-hook method but also works within MIME digests.
     
    2325: '''Note:''' The way #2 ('''message-hook''') '''was''' triggering an infinite loop bug in old Mutts. Bug solved long ago: Upgrade.
    2426
    25 : '''Note:''' You may have previously found adviced here and there some weird procmail recipes changing inline text to app/pgp so Mutt can deal with the message. Those are old dirty hacks that at first may have seemed to work, but solving one problem created three others. Today: Avoid at all costs.
    26 
     27: '''Note:''' Avoid any random advice to use procmail recipe to change inline text to app/pgp so Mutt can deal with the message. This is an old dirty hack that at first may have seemed to work, but solving one problem created three others. Today: Avoid at all costs.
    2728
    2829Since some coders of mutt established RFCs for usage of PGP
    2930secured eMail with MIME (2015, 3156, see RelevantStandards) to
    30 make lives easier for users (and clients), avoid creating oldstyle
    31 PGP eMails, let mutt do it right.
     31make lives easier for users (and clients), avoid creating old style
     32PGP email, let mutt do it right.
    3233
    33 If for some ''stuck with old software''-reason you insist on
    34 producing them, adjust '''$pgp_create_traditional''' to your
     34If for some ''stuck with old software''-reason you insist on producing them, adjust '''$pgp_create_traditional''' to your
    3535needs.
    3636
     
    4545 reply-hook . set crypt_autosign = yes
    4646
    47 
    48 === I typed wrong passphrase, but mutt still keeps using it? ===
     47=== I typed wrong the passphrase, but mutt still keeps using it? ===
    4948Maybe your PGP commands return bad exit codes for errors. See "?"
    5049for how to '''forget-passphrase'''.
     
    6766to ~/.gnupg/gpg.conf (~/.gnupg/options in gpg 1.0).
    6867You can alternatively add it in Mutt's crypt_* options.
    69 But <b>BEWARE</b> of the security implications this has.
    70 Basically you're adding another vulnerability to the encrypted message.
    71 If your <i>or</i> the recipient's key is compromised an attacker can read the message.
     68But '''BEWARE''' of the security implications this has.
     69Basically, this adds another vulnerability to the encrypted message.
     70If either sender '''or''' the receiver key is compromised, an attacker can read the message.
    7271
    7372Another even less secure possibility is to save your local copy unencrypted. See mutt's $fcc_clear.