Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id B5901431FDA for ; Sat, 11 Oct 2014 04:46:48 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l9Fjf+sDK4JK for ; Sat, 11 Oct 2014 04:46:43 -0700 (PDT) Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108]) by olra.theworths.org (Postfix) with ESMTP id 3703A431FD0 for ; Sat, 11 Oct 2014 04:46:43 -0700 (PDT) Received: from fifthhorseman.net (h-67-100-110-147.nycm.ny.dynamic.megapath.net [67.100.110.147]) by che.mayfirst.org (Postfix) with ESMTPSA id D7BDAF984 for ; Sat, 11 Oct 2014 07:46:34 -0400 (EDT) Received: by fifthhorseman.net (Postfix, from userid 1000) id B84E4201AB; Sat, 11 Oct 2014 07:46:34 -0400 (EDT) From: Daniel Kahn Gillmor To: notmuch mailing list Subject: process-crypto failing when encountering an unknown algorithm User-Agent: Notmuch/0.18.1 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Sat, 11 Oct 2014 07:46:28 -0400 Message-ID: <87fveu25ij.fsf@alice.fifthhorseman.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 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: Sat, 11 Oct 2014 11:46:48 -0000 --=-=-= Content-Type: text/plain hi folks-- sorry to not have a clearer debugging statement right no (ENOTIME to generate something nice) but i think notmuch-emacs was failing to render a thread for me when one of the messages involved was either signed with or encrypted using an algorithm that gpg didn't know about. I ran into this because i'm working on gpg 2.1, which implements some OpenPGP elliptic curve crypto. notmuch really shouldn't just fail to render the entire thread in the event that it sees an unknown algorithm -- it should just show the encrypted message and indicate failure to decrypt. If i can get more time, i'll try to dig deeper and craft an example message, and a proper bug report, but if anyone else can do that part, i'd appreciate it. --dkg --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQJ8BAEBCgBmBQJUORiVXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQjk2OTEyODdBN0FEREUzNzU3RDkxMUVB NTI0MDFCMTFCRkRGQTVDAAoJEKUkAbEb/fpcLtcP/iIb1y+1ZapUXNOFqbrClUJD TlyLHCtA+BNI51XyB3nEmpyvpAkH+TtCOMQLaCFiCz/6jeGiyLTc/Mwhbf2E/HyV 3tbSrF6SjwrT0K44aOkhwwnO24RXhjgtuoTSnDNlecmA+W2vwEz97L5D6Rz2pU7e M9U7EGHy0PHpjsERnDZe08L0+lMVPVMyw3c/ZaASk2RNsDpow9eRS+bz9bVTOozn M5mgZaxLEewb3E91mioJxXm+KMsmBeB/wGLErx2VHqAHSdtimT721cD82+PbSrFB j8m3Nzjq9XKrLuwPR0JYWe2kf7r63sVW8tIaAWeNNgdmvZe+m8bq10S/vLw9N4yC oUw7wKyaIUa98g7NIa4hXP1/VEgBM/XYehbHGTHkviNxxccdNZ0Twz+5cxHOL0fP ig49dMZqFOJ/+my+fVKpv2VfjWzDknRFSWAEK006fCZBjcJO1aY9rrcv/puw4p2/ J7+sG5HpECeec4sfsZKQrIgoNOO0v2xKN+BmvwXQ8Vec1l65WS5STGPOAPKWCO2R Yj4nclWPszQN6IQJwcHyxQKC35JtqB6EEORlkIVNS1VaI10rEKfhrDeHEkFcj6hX 9agYSebKx2gqVPMJXoDY7c+l8wLNrevx6ZmsL4BIs7ms3Vi499nnGpUOumqadH5/ MGTD7W71dEWUVJoGA0N3 =QE8z -----END PGP SIGNATURE----- --=-=-=--