Re: Bcc, throw-keyids, and metadata hiding [was: Re: Announcing Astroid v0.11]

2018-02-05 Thread Gaute Hope
Daniel Kahn Gillmor writes on februar 5, 2018 9:33: On Mon 2018-02-05 08:33:36 +0100, Gaute Hope wrote: Yes; this seems like the ultimate approach to this problem, unless it will be possible for GPG to completely hide receivers - I am guessing this is inherently impossible? I'm not sure how

Re: Bcc, throw-keyids, and metadata hiding [was: Re: Announcing Astroid v0.11]

2018-02-05 Thread Daniel Kahn Gillmor
On Mon 2018-02-05 08:33:36 +0100, Gaute Hope wrote: > Yes; this seems like the ultimate approach to this problem, unless > it will be possible for GPG to completely hide receivers - I am guessing > this is inherently impossible? I'm not sure how gpg could do that -- the metadata leak of most

Re: Bcc, throw-keyids, and metadata hiding [was: Re: Announcing Astroid v0.11]

2018-02-04 Thread Gaute Hope
Daniel Kahn Gillmor writes on februar 5, 2018 2:21: On Sun 2018-02-04 16:18:02 -0500, Daniel Kahn Gillmor wrote: Well, i guess you could limit it to two copies total: one copy is to all Bcc'ed recipients, and one copy to all non-Bcc'ed recipients. you'd want to make sure that you got the same

Bcc, throw-keyids, and metadata hiding [was: Re: Announcing Astroid v0.11]

2018-02-04 Thread Daniel Kahn Gillmor
On Sun 2018-02-04 16:18:02 -0500, Daniel Kahn Gillmor wrote: > Well, i guess you could limit it to two copies total: one copy is to all > Bcc'ed recipients, and one copy to all non-Bcc'ed recipients. you'd > want to make sure that you got the same Message-ID on each generated > copy, of course. >

Re: Announcing Astroid v0.11

2018-02-04 Thread Daniel Kahn Gillmor
On Sun 2018-02-04 20:10:25 +0100, Gaute Hope wrote: > Because that is currently the only option when using GMime [0]. right, sad. and that's likely due to the constraints of GPGME. what a dependency chain! I've just opened two issues to try to push that forward:

Re: Announcing Astroid v0.11

2018-02-04 Thread Gaute Hope
Daniel Kahn Gillmor writes on februar 4, 2018 19:32: On Sun 2018-02-04 18:52:22 +0100, Gaute Hope wrote: This is done to hide Bcc-recipients. sure, but i'm wondering why you throw *all* keyids, instead of only the key-ids of the bcc'ed people? Because that is currently the only option when

Re: Announcing Astroid v0.11

2018-02-04 Thread Daniel Kahn Gillmor
On Sun 2018-02-04 18:52:22 +0100, Gaute Hope wrote: > This is done to hide Bcc-recipients. sure, but i'm wondering why you throw *all* keyids, instead of only the key-ids of the bcc'ed people? > As you say, GnuPG must try all the secret keys; but many > users use some sort of keyring to unlock

Re: Announcing Astroid v0.11

2018-02-04 Thread Gaute Hope
Daniel Kahn Gillmor writes on februar 4, 2018 16:37: On Sun 2018-02-04 11:46:20 +0100, Gaute Hope wrote: * 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

Re: Announcing Astroid v0.11

2018-02-04 Thread Daniel Kahn Gillmor
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

Announcing Astroid v0.11

2018-02-04 Thread Gaute Hope
Greetings, Astroid v0.11 has been released! Astroid is a lightweight and fast graphical threads-with-tags email client for notmuch. Written in C++ using GTK+, WebKit and gmime. Astroid can be acquired, along with usage and instructions for use, at: https://github.com/astroidmail/astroid