unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Gaute Hope <eg@gaute.vetsj.com>,
	astroidmail@googlegroups.com, notmuch@notmuchmail.org
Subject: Re: Announcing Astroid v0.11
Date: Sun, 04 Feb 2018 10:37:50 -0500	[thread overview]
Message-ID: <87y3k822b5.fsf@fifthhorseman.net> (raw)
In-Reply-To: <1517741078.emojmmucvz.astroid@strange.none>

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

Hi Gaute--

On Sun 2018-02-04 11:46:20 +0100, Gaute Hope wrote:
> Astroid v0.11 has been released!

Congratulations -- it's great to see this progress! :)

> * Always throw key-id when sending (using GMime 3)

Can you explain this choice?  As someone who receives mail with a thrown
key-id, and as someone who has multiple secret keys, the user experience
of receiving encrypted mail like this is *terrible*.  (terrible to the
point of me wanting to ask people who do this for normal mail to just
send me mail in the clear in the future :( )

In particular: GnuPG doesn't know which key to use, so it prompts me for
passphrases for *all* of the secret keys i control, in succession.

I understand the desire to reduce metadata leakage.  But if you're
wrapping the PGP/MIME application/pgp-encrypted part in an RFC822
message that contains a header with the person's e-mail address anyway,
it's not clear that there has been a significant reduction of cleartext
metadata.  So this seems like a bad tradeoff for any case where the
recipient is explicitly specified (i.e., not in Bcc:)

Regards,

        --dkg

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

  reply	other threads:[~2018-02-04 17:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04 10:46 Announcing Astroid v0.11 Gaute Hope
2018-02-04 15:37 ` Daniel Kahn Gillmor [this message]
2018-02-04 17:52   ` Gaute Hope
2018-02-04 18:32     ` Daniel Kahn Gillmor
2018-02-04 19:10       ` Gaute Hope
2018-02-04 21:18         ` Daniel Kahn Gillmor
2018-02-05  1:21           ` Bcc, throw-keyids, and metadata hiding [was: Re: Announcing Astroid v0.11] Daniel Kahn Gillmor
2018-02-05  7:33             ` Gaute Hope
2018-02-05  8:33               ` Daniel Kahn Gillmor
2018-02-05 15:15                 ` Gaute Hope
2018-02-20 10:08 ` Announcing Astroid v0.11.1 Gaute Hope
2018-02-20 10:28   ` David Bremner

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=87y3k822b5.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=astroidmail@googlegroups.com \
    --cc=eg@gaute.vetsj.com \
    --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).