Hello dkg,
On Sat 09 Nov 2019 at 04:57PM -05, Daniel Kahn Gillmor wrote:
> Thanks for your thoughtful and helpful feedback.
Of course! Series applied to master, except for a few commit message
edits (I was worried that we are quoting too much of the gpg manpage).
> On Sat 2019-11-09 08:46:34 -
Hi Sean--
Thanks for your thoughtful and helpful feedback. I've just sent a
revised series (5 patches) that takes into account everything that you
said.
I've declined to adopt two suggestions (please see my reasons below):
On Sat 2019-11-09 08:46:34 -0700, Sean Whitton wrote:
>> diff --git a/de
Hello,
On Fri 08 Nov 2019 at 09:03AM -05, Daniel Kahn Gillmor wrote:
> On Fri 2019-11-08 02:10:48 -0500, Daniel Kahn Gillmor wrote:
>> +out:subprocess.CompletedProcess[bytes] =
>> subprocess.run(['gpg', '--decrypt'],
>> +
Hello,
On Fri 08 Nov 2019 at 02:10AM -05, Daniel Kahn Gillmor wrote:
> In some cases, the user may want to try to use their own GnuPG secret
> keys to decrypt encrypted parts of the message.
>
> By default it is disabled so that we aren't accidentally triggering
> the use of user secret key mater
On Fri 2019-11-08 02:10:48 -0500, Daniel Kahn Gillmor wrote:
> +out:subprocess.CompletedProcess[bytes] =
> subprocess.run(['gpg', '--decrypt'],
> +
> stdin=inp,
> +
In some cases, the user may want to try to use their own GnuPG secret
keys to decrypt encrypted parts of the message.
By default it is disabled so that we aren't accidentally triggering
the use of user secret key material.
Signed-off-by: Daniel Kahn Gillmor
---
debian/control
6 matches
Mail list logo
