unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Amin Bandali <bandali@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Signing emails with mu4e (was Re: Hello, new committer here!)
Date: Tue, 01 Sep 2020 19:00:48 -0400	[thread overview]
Message-ID: <87tuwhyue7.fsf@gnu.org> (raw)
In-Reply-To: <87ft81pqkl.fsf@ambrevar.xyz>

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

Pierre Neidhardt writes:

> This is what I do to sign all my messages:
>
> (add-hook 'message-setup-hook 'mml-secure-sign-pgpmime)
>
[...]

A word of caution: at least with Gnus, doing something like this might
"downgrade" the security of a message, by changing it to only sign the
message you're composing when normally it would have been both signed
and encrypted.  It typically happens when replying to an encrypted
message.

For that reason, I set the message to be signed only when it's not being
signed+encrypted:

    (add-hook 'gnus-message-setup-hook
              (lambda ()
                (unless (mml-secure-is-encrypted-p)
                  (mml-secure-message-sign))))

For non-Gnus users, I'd imagine replacing `gnus-message-setup-hook' with
`message-setup-hook' would work.

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

  reply	other threads:[~2020-09-01 23:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 10:52 Hello, new committer here! Pierre Langlois
2020-09-01 12:11 ` Signing emails with mu4e (was Re: Hello, new committer here!) Pierre Langlois
2020-09-01 12:29   ` Pierre Langlois
2020-09-01 13:06     ` Efraim Flashner
2020-09-01 13:35     ` Pierre Neidhardt
2020-09-01 23:00       ` Amin Bandali [this message]
2020-09-02 10:15         ` Pierre Langlois
2020-09-04 17:16     ` Signing emails with Emacs 27.1 Giovanni Biscuolo
2020-09-04 17:47       ` Pierre Langlois
2020-09-07  9:19 ` Hello, new committer here! Ludovic Courtès

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87tuwhyue7.fsf@gnu.org \
    --to=bandali@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).