From: "Antoine Beaupré" <anarcat@debian.org>
To: Notmuch list <notmuch@notmuchmail.org>
Cc: dkg@fifthhorseman.net, dme@dme.org
Subject: Re: revisiting Autocrypt in notmuch, MVP
Date: Thu, 22 Feb 2024 22:22:13 -0500 [thread overview]
Message-ID: <87plwn6f16.fsf@angela.anarc.at> (raw)
In-Reply-To: <87mt2utszi.fsf@angela.anarc.at>
On 2023-04-26 12:10:09, Antoine Beaupré wrote:
[...]
> And while autocrypt has a nice beautiful and brilliant spec that does
> everything, that's not what I'm looking at right now. And I don't think
> it's productive to block in this way at this point.
>
> So I made a bespoke implementation that just calls out to sequoia (and
> yes, also gpg, hopefully one day the latter can just go away) to insert
> autocrypt headers to outgoing mail. Here's the implementation:
>
> https://gitlab.com/anarcat/emacs-d/-/blob/354fabad24100f69310dd16a0d30ac3bd96d7244/notmuch-config.el#L14-31
>
> It's brittle, but it works for my case.
>
> I don't think this is something that can be merged as-is in notmuch. It
> depends on gnupg and sequoia, and it's probably incorrect as far as the
> Autocrypt spec is concerned (in particular it doesn't use a UID to
> fingerprint map), but this all seems like things could be improved.
A small update on this: I just realized I was sending autocrypt headers
regardless of whether or not I was signing / encrypting mails. I'm not
sure this is a good idea. The spec says that I "SHOULD", I believe:
https://autocrypt.org/level1.html#header-injection-in-outbound-mail
... but it feels a bit too intrusive... Do I really want to divulge my
cryptographic identity to the world constantly? I'm using ed25519 keys
now, so the header is small, but for other users, that grows the message
size significantly...
Patch is:
https://gitlab.com/anarcat/emacs-d/-/commit/c79495f8580735c23748a62db99b3d9f34f413f5
Interestingly, i had to make a new mml-* function; there's a predicate
to check if a message is encrypted, but not if it's signed, which seems
silly. So I vendored and improved the code, which also feels silly.
So there you go, diverging from the standard already. :)
A.
--
You Are What You Is
- Frank Zappa\r
next prev parent reply other threads:[~2024-02-23 3:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 18:10 revisiting Autocrypt in notmuch, MVP Antoine Beaupré
2024-02-23 3:22 ` Antoine Beaupré [this message]
2024-02-23 17:14 ` Antoine Beaupré
2024-02-25 4:09 ` Steven Allen
2024-02-25 9:40 ` Sandra Snan
2024-02-25 16:33 ` Steven Allen
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=87plwn6f16.fsf@angela.anarc.at \
--to=anarcat@debian.org \
--cc=dkg@fifthhorseman.net \
--cc=dme@dme.org \
--cc=notmuch@notmuchmail.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.
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).