| 1 |
On Wed, Jan 31, 2018 at 05:17:45AM +0100 , Floyd Anderson wrote: |
| 2 |
> I would not do that. The topic itself is complex enough and sourcing of 14 ! |
| 3 |
> long and cryptic command lines doesn’t make it better. Also note that gpg.rc |
| 4 |
> defines the deprecated ‘pgp_clearsign_command’ variable. |
| 5 |
Right. |
| 6 |
|
| 7 |
> BTW. as we‘re talking about NeoMutt here, I use: |
| 8 |
> ${XDG_CONFIG_HOME:-${HOME}/.}${XDG_CONFIG_HOME:+/}neomutt/neomuttrc |
| 9 |
> so I can run a parallel Mutt installation when things get broken. |
| 10 |
That is a very good point. |
| 11 |
|
| 12 |
> Instead I suggest to set ‘gpgme’ USE-flag and *only that* – no ‘crypt’, |
| 13 |
> ‘gpg’, ‘pgp_classic’, ‘smime’, ‘smime_classic’. Look at the ebuild and |
| 14 |
> especially the comments. This way I only need to set one ! variable to get |
| 15 |
> the stuff working: |
| 16 |
> |
| 17 |
> set crypt_use_gpgme = yes |
| 18 |
> |
| 19 |
> |
| 20 |
> To be sure you may also set: |
| 21 |
> # ensure deprecated options are disabled or disarmed |
| 22 |
> set pgp_autoinline = no |
| 23 |
> set pgp_clearsign_command = '' |
| 24 |
> set pgp_mime_auto = ask-yes |
| 25 |
> set pgp_replyinline = no |
| 26 |
> |
| 27 |
> And if one like: |
| 28 |
> # semi-automated encrypted reply to encrypted messages |
| 29 |
> # Notes: |
| 30 |
> # - this can always be disabled by PGP-menu ('p') |
| 31 |
> # - crypt_autoencrypt or crypt_replyencrypt (if set) disables crypt_opportunistic_encrypt |
| 32 |
> set crypt_opportunistic_encrypt = yes |
| 33 |
> set crypt_autoencrypt = no |
| 34 |
> set crypt_replyencrypt = no |
| 35 |
> |
| 36 |
> # whether or not display unusable (revoked, expired, disabled) keys |
| 37 |
> set pgp_show_unusable = yes |
| 38 |
> set crypt_timestamp = no |
| 39 |
> |
| 40 |
> |
| 41 |
> With more than one mail address I suggest: |
| 42 |
> send2-hook . 'set pgp_sign_as = ""' |
| 43 |
> send2-hook '~f "1st@example\.net$"' 'set pgp_sign_as = "0x0123456789ABCDEF0123456789ABCDEF01234567"' |
| 44 |
> send2-hook '~f "2nd@example\.net$"' 'set pgp_sign_as = "0xABCDEF0123456789ABCDEF0123456789ABCDEF01"' |
| 45 |
Thanks for the above, I will certainly revisit this email when I update |
| 46 |
my config in the next month or so. :) |
| 47 |
|
| 48 |
> |
| 49 |
> > On my neomutt, when I press "v" to view attachments, all I can |
| 50 |
> > see is text/plain. I think my neomutt does something automatic to |
| 51 |
> > decrypt the messages. |
| 52 |
> > |
| 53 |
> |
| 54 |
> Indeed, viewing attachments encrypted would break many functions otherwise, |
| 55 |
> e.g. piping, printing, saving. |
| 56 |
So Lucas's original problem sounds like an issue with this, I can only |
| 57 |
imagine it is some sort of lack of pgp support. |
| 58 |
|
| 59 |
> > My source docs I used when setting my gpg up with mutt were: |
| 60 |
> > https://gitlab.com/muttmua/mutt/wikis/MuttGuide/UseGPG |
| 61 |
> > http://codesorcery.net/old/mutt/mutt-gnupg-howto |
| 62 |
> > |
| 63 |
> |
| 64 |
> In the meantime NeoMutt != Mutt, so not to forget to mention |
| 65 |
> <https://www.neomutt.org/guide/>. ;-) |
| 66 |
Lol. Of course. I read that for my current setup. Though I never really |
| 67 |
got to grips with what gpgme was, as I was more concerned with |
| 68 |
bootstrapping a working (neo)mutt configuration, which is why I source |
| 69 |
my : "14 ! long and cryptic command lines". |
| 70 |
|
| 71 |
Thanks for the critique Floyd. |
| 72 |
|
| 73 |
-- |
| 74 |
|
| 75 |
Roger Welsh |
| 76 |
fpr: 2FCB 9E31 EA77 CDEC A3AE 5DD7 D54C C777 553A 180D |
Archives