unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Gregor Zattler <Gregor@shi>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
	Gregor Zattler <telegraph@gmx.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: Emacs: Crypto: How to get automatic encryption?
Date: Wed, 04 Jan 2012 01:08:33 +0100	[thread overview]
Message-ID: <87y5toqqgu.fsf@shi.workgroup> (raw)
In-Reply-To: <87fwfw8npx.fsf@servo.finestructure.net>

Hi Jamie, notmuch developers,
On Tue, 03 Jan 2012 13:45:14 -0800, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> On Tue, 3 Jan 2012 20:56:51 +0100, Gregor Zattler <telegraph@gmx.net> wrote:
> > I replied to a PGP/MIME signed and encrypted e-mail and was
> > astonished to realise that my reply was sent unencrypted (and
> > unsigened for that matter).
> 
> Yikes!  Sorry this happened, and I hope nothing too sensitive was
> exposed.

No :-)

> Auto signing of outgoing mail can be enabled by the following [0]:
> 
> (add-hook 'message-setup-hook mml-secure-message-sign-pgpmime)
> 
> You can configure the message-setup-hook with the customization UI as
> well.

I tried this and enabled mml-secure-message-encrypt-pgpmime too.
I did a test with an address I have no public key for.  I was
informed of the fact and asked if I want to skip this key.  The
result was an email encrypted only to me (I suppose it's a
sensible default to include the key of the sender in the list of
key to encrypt to), so it would be unreadable for the recipient :-(

> Unfortunately, auto encrypting of replies to encrypted emails is not yet
> implemented.  It is desperately needed, though, obviously.  So this is a
> good excuse to start a discussion about how we could achieve this.
> 
> It just occurs to me that a way to do this would be to have notmuch
> reply add the appropriate mml #secure tag for encryption to the output
> reply template, maybe with something like a --emacs option.  That would
> be pretty easy to implement, although it would obviously be very UI
> specific.
> 
> Another possibility would be for notmuch reply to add some sort of
> header to the reply message to indicate that the original was encrypted,
> and then do something in emacs to try to read that header and add the
> appropriate mml #secure tag.  That would also be easy to implement in
> the notmuch CLI, and it would be more UI agnostic, but it would require
> a lot more elisp.
> 
> Or maybe we could support both?
> 
> Any other suggestions?

I'm no developer; your second suggestion sounds more plausible
me since notmuch is a frontend-agnostic mail system.

> > Actually the message buffer in which I write replies has Auto
> > Encryption Mode enabled, but nothing happens.  
> 
> That's unfortunate.  Can you explain exactly how you set this up, and
> how it didn't work?

Actually I did not set it up.  I tested this again with emacs23
-q ...  It has something to do with EasyPG and therefore I assume
it only works on the level of file encryption if the file
associated with the buffer ends in .pgp  But that's a guess.


[...]
> It's actually usually mml that is used with message-mode to
> sign/encrypt message, not epg.

Thanks for your info.  Actually I'm a mutt user and I customised
mutt to opportunistically encrypt emails if I/gpg have/has public
keys for all recipients of an email.  I have no clue how to
achieve this with Emacs.

Ciao; Gregor

  reply	other threads:[~2012-01-04  0:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 19:56 Emacs: Crypto: How to get automatic encryption? Gregor Zattler
2012-01-03 21:45 ` Jameson Graef Rollins
2012-01-04  0:08   ` Gregor Zattler [this message]
2012-01-04  8:36   ` David Edmondson
2012-01-04  8:48     ` David Edmondson
2012-01-15 22:27       ` Gregor Zattler
2012-01-17  4:48         ` Antoine Beaupré
2012-01-17  9:19           ` David Edmondson
2012-01-17 16:12             ` Antoine Beaupré
2012-01-24 21:34             ` micah anderson
2012-01-25  0:10               ` Jameson Graef Rollins
2012-01-25  6:23                 ` David Edmondson
2012-01-25  9:26                   ` Jameson Graef Rollins
2012-01-25 10:20                     ` David Edmondson
2012-01-25 17:45                       ` Jameson Graef Rollins
2012-01-25 19:09                         ` Daniel Kahn Gillmor
2012-01-26  8:53                         ` David Edmondson
2012-01-17 15:39           ` David Edmondson
2012-01-12 18:41   ` Jameson Graef Rollins
2012-01-12 19:05     ` Gregor Zattler
2012-01-12 19:28       ` Jameson Graef Rollins
2012-01-12 19:29       ` Darren McGuicken

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://notmuchmail.org/

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

  git send-email \
    --in-reply-to=87y5toqqgu.fsf@shi.workgroup \
    --to=gregor@shi \
    --cc=jrollins@finestructure.net \
    --cc=notmuch@notmuchmail.org \
    --cc=telegraph@gmx.net \
    /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://yhetil.org/notmuch.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).