Gnus development mailing list
 help / color / mirror / Atom feed
From: Xavier Maillard <lists.emacs.gnus@xavier.maillard.im>
To: ding@gnus.org
Subject: Re: Maybe encrypt message ?
Date: Tue, 24 Nov 2015 21:53:13 +0100	[thread overview]
Message-ID: <m0egffxgp2.fsf@kcals.intra.maillard.im> (raw)
In-Reply-To: <878u5nfv4u.fsf@mat.ucm.es> (Uwe Brauer's message of "Tue, 24 Nov 2015 12:18:41 +0000")

[-- Attachment #1: Type: text/plain, Size: 2309 bytes --]

Uwe Brauer <oub@mat.ucm.es> writes:

>>>> "Xavier" == Xavier Maillard <lists.emacs.gnus@xavier.maillard.im> writes:
>
>     > Hello,
>     > what is the correct way to tell gnus/message to 'maybe' encrypt an outgoing
>     > message ?
>
>     > I previously set it via `message-setup-hook' by adding
>     > `mml-secure-message-encrypt'. For a reason I do not understand, it encrypted
>     > *ALL* outgoing messages (even on mailing-lists). That's lame since for some, I
>     > remember having been asked to ignore encryption for recipient I did not have a
>     > public key...
>
>     > How do you practice PGP encryption/signing in Gnus ?
>
> There are three possiblities.

[ ... cut ... ]

>     -  You can use  have an entry in your  bbdb.
>     For example
>     encrypt: smime
>     or
>     encrypt: gpg
>     than gnus encrypt using smime or gpg
>
>      Or nothing gnus does not do anything.

I remember that possibility now ! If I could sync my carddav with bbdb, maybe
I could get back to using it.

>     -  However if I also want to sign my message than this approach is
>        too restrictive. So I have a yes-o-no function in my
>        message-send-hook namely my-hook-encrypt-or-sign-smime
>
> (defun my-hook-encrypt-or-sign-smime ()
>   (interactive)
>   (call-interactively 'my-select-encrypt-or-sign-smime))
>
> (defun my-leave-the-TAG ()
>   (interactive)
>   (message "Left the TAG intact, since it is a pgp/(mime) message."))
>
> (defun my-select-encrypt-or-sign-smime (ch) 
>   (interactive "c1: encrypt, 2: encryt+sign, 3: sign 4: NO TAG 5: leave it: pgp/mime")
>   (setq ch (downcase ch))
>   (call-interactively (cond ((eql ch ?1) #'my-only-encrypt-smime)
>                             ((eql ch ?2) #'my-encrypt-and-sign-smime)
>                             ((eql ch ?3) #'mml-secure-message-sign-smime)         
>                             ((eql ch ?4) #'my-mml-eliminate-smime-pgp-tag)
>                             ((eql ch ?5) #'my-leave-the-TAG)
>                             (t (error 'args-out-of-range '(1 2 3 4 5 ch))))))
>
> You could do something similar for gpg instead of smime.

Isn't this too cumbersome ? For each of your outgoing message, you have to
make a choice, right ?

Thanks,

-- Xavier.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2015-11-24 20:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24  6:10 Xavier Maillard
2015-11-24 12:18 ` Uwe Brauer
2015-11-24 20:53   ` Xavier Maillard [this message]
2015-11-25 11:03     ` Uwe Brauer
2015-11-24 16:22 ` Jens Lechtenboerger
2015-11-24 20:48   ` Xavier Maillard
2015-11-24 21:17 ` Peter Münster
2015-11-25 11:04   ` Uwe Brauer
2015-11-26  5:00   ` Xavier Maillard
2015-11-26 10:11     ` Peter Münster
2015-11-26 14:44       ` Xavier Maillard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m0egffxgp2.fsf@kcals.intra.maillard.im \
    --to=lists.emacs.gnus@xavier.maillard.im \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).