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 F21796DE2013 for ; Tue, 28 Feb 2017 18:18:13 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.005 X-Spam-Level: X-Spam-Status: No, score=-0.005 tagged_above=-999 required=5 tests=[AWL=0.006, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 xPLWYkT7AGLF for ; Tue, 28 Feb 2017 18:18:13 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 421716DE1F87 for ; Tue, 28 Feb 2017 18:18:13 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1citpd-0005BW-9d; Tue, 28 Feb 2017 21:17:33 -0500 Received: (nullmailer pid 14845 invoked by uid 1000); Wed, 01 Mar 2017 02:18:10 -0000 From: David Bremner To: Sebastian Schwarz , notmuch@notmuchmail.org Subject: Re: [RFE] Call `gpg --recv-keys` asynchronously In-Reply-To: <8760jtx484.fsf@tethera.net> References: <87poi2vyti.fsf@bistromath> <878toq9d2n.fsf@domain.invalid> <8760jtx484.fsf@tethera.net> Date: Tue, 28 Feb 2017 22:18:10 -0400 Message-ID: <87lgspvixp.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.22 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: Wed, 01 Mar 2017 02:18:14 -0000 David Bremner writes: > Sebastian Schwarz writes: > >> Allow me add to this RFE. >> >> On 2017-02-28, Steven Allen wrote: >>> Currently, notmuch fetches keys synchronously. This can be >>> *very* slow (I fetch keys over tor) and locks up emacs for the >>> duration. Therefore, this fetch really should be >>> asynchronous. >> >> Even with all keys already present signature verification takes >> some time as well. It would be nice if this was done >> asynchronously as well. This would greatly improve the speed of >> opening threads with large numbers of signed messages. > > Offhand, that sounds even harder. With a noticable loss in security, we > could cache the verifications in the database so the cost is only paid > once. > > d FWIW, these changes are pretty unrelated at an implimentation level. The key fetching is done from emacs, while the verification is done in the notmuch binary. d