From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 589336DE0ACB for ; Thu, 30 Nov 2017 07:58:39 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.01 X-Spam-Level: X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[AWL=-0.010] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7eHTIws-nbFm for ; Thu, 30 Nov 2017 07:58:38 -0800 (PST) Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) by arlo.cworth.org (Postfix) with ESMTPS id 158C06DE0119 for ; Thu, 30 Nov 2017 07:58:37 -0800 (PST) Received: from fifthhorseman.net (ool-6c3a0662.static.optonline.net [108.58.6.98]) by che.mayfirst.org (Postfix) with ESMTPSA id 93911F99B; Thu, 30 Nov 2017 10:58:36 -0500 (EST) Received: by fifthhorseman.net (Postfix, from userid 1000) id 9A90B202DB; Thu, 30 Nov 2017 10:57:12 -0500 (EST) From: Daniel Kahn Gillmor To: David Bremner , Notmuch Mail Subject: Re: [PATCH 15/18] crypto: actually stash session keys when try-decrypt=true In-Reply-To: <87tvxu8jwl.fsf@tethera.net> References: <20171025065203.24403-1-dkg@fifthhorseman.net> <20171025065203.24403-16-dkg@fifthhorseman.net> <87tvxu8jwl.fsf@tethera.net> Date: Thu, 30 Nov 2017 10:57:12 -0500 Message-ID: <87tvxb3gkn.fsf@fifthhorseman.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2017 15:58:39 -0000 On Thu 2017-11-16 08:53:14 -0400, David Bremner wrote: > I'd be happier if we didn't further entrench the text format in the test > suite. How hard would it be to use json output (+maybe python?) here? json output seems clunkier to me, and i don't think it's necessary for the purposes of these tests. Using python here isn't possible without updating the python bindings to accomodate decryption policy, which doesn't come until later in the series. so i'd prefer to leave it as-is, but i wouldn't object if someone wanted to propose a good patch to these tests that uses json. --dkg