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 9B838431FD0 for ; Tue, 27 Dec 2011 06:23:23 -0800 (PST) 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 9iuBoZHLXuTl for ; Tue, 27 Dec 2011 06:23:21 -0800 (PST) Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108]) by olra.theworths.org (Postfix) with ESMTP id BD536431FB6 for ; Tue, 27 Dec 2011 06:23:21 -0800 (PST) Received: from [192.168.1.91] (adsl-74-242-247-77.rmo.bellsouth.net [74.242.247.77]) by che.mayfirst.org (Postfix) with ESMTPSA id 04F3EF970 for ; Tue, 27 Dec 2011 09:23:16 -0500 (EST) Message-ID: <4EF9D4CE.5020502@fifthhorseman.net> Date: Tue, 27 Dec 2011 09:23:10 -0500 From: Daniel Kahn Gillmor User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111120 Icedove/8.0 MIME-Version: 1.0 To: "notmuch@notmuchmail.org" Subject: Re: S/MIME support in notmuch References: <87iplrwz0k.fsf@bryandb1-ll1.dom1.jhuapl.edu> <87aa6m6t3u.fsf@bookbinder.fernseed.info> <87mxajnsvq.fsf@bryandb1-ll1.dom1.jhuapl.edu> In-Reply-To: <87mxajnsvq.fsf@bryandb1-ll1.dom1.jhuapl.edu> X-Enigmail-Version: 1.3.3 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig276FAFE17C426E398309EA34" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: notmuch List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Dec 2011 14:23:23 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig276FAFE17C426E398309EA34 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 12/23/2011 11:40 AM, Dan Bryant wrote: > On Wed, 21 Dec 2011 06:51:01 -0500, Darren McGuicken wrote: >> When you make those changes to the gpg_context are you breaking gpg >> signature validation? Or is the one a superset of the other? >=20 > The current assumption in notmuch is that all encrypted/signed messages= > in a mailbox will be using the same crypto algorithm. This is the first= > thing I want to fix: which crypto algorithm (and therefore, context > object) to use should probably be detected by the MIME type of the > message part. This was an issue i was hoping would get resolved in gmime 2.6, but apparently it's still open: https://bugzilla.gnome.org/show_bug.cgi?id=3D641848 So it does look like we're going to need to do the detection and selecion ourselves. --dkg --------------enig276FAFE17C426E398309EA34 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQJ8BAEBCgBmBQJO+dTOXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwRUU1QkU5NzkyODJEODBCOUY3NTQwRjFD Q0QyRUQ5NEQyMTczOUU5AAoJEMzS7ZTSFznpDMsP/RE517IVhwqYtZYF/KsJoylE bRhOSh5UTIddj1M56oSPirF3FFQVhmYTIzwAPMGcs6A7ssOmTybUJwCD1T8Xa4pY ef1GnWkYN3KTxyZ80Q4BO8SBOJU7o/9TC/hkVeELL1gVhLHwLEYtw0uXo6ZSqexM MqMogiOGeNPXNh1NWBrnhPA2zAOZNcJ9oRlyygbkjRlshbYszlN8lhhlvC8S2g37 MpPK+1oyR8oHNDLab1RyRc1t6xGl76dHjrlsc74kJzG7vD96BNp2FiY86aVD9Dw4 ISx2TXB38x1NZwTkevyQJLLMqYGPTPLfFk0LMmL0C8fi5FlB0I26K2cmMy5MUzQO qlrmvxJPxTdwLT2ahUkqI2SLMSvuAbG3UwT4bybVpA2HA0Wv6mWyw6mX2IMUavQ7 kxmgvNBrbj5+Ggkcu5kHUQEPQpiO8ItkKJ0a3aIQfQzurpWJ6OweZZgcokOKxjt2 i1C/ssBttxGFICjx/Q75KU331sqsm+CuZi4PtdBFeCbkl/X4g6M6Xo2KmeLK0gFV T9rUUlgsaMPOZwGaBtseMfnTle5hbrnDgx2+OPe7vasqdmNiXRjW2WjqgJos7tU6 5u94YHQphrb88WjSloA3fTTfYwUZe+N1YIPSZ1puQNZXm0vZnI4JdzRMuv5qhDZJ QtUDPTcsdrSei7wdj434 =zghN -----END PGP SIGNATURE----- --------------enig276FAFE17C426E398309EA34--