Message-ID: <4D10C97C.7060602@fifthhorseman.net>
Date: Tue, 21 Dec 2010 10:36:28 -0500
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.2.12) Gecko/20101110 Icedove/3.1.6
MIME-Version: 1.0
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: PGP/MIME signature verification
References: <4CF15D67.1070904@fifthhorseman.net>
	<87aak08fu8.fsf@servo.finestructure.net>
	<87zkrz314j.fsf@SSpaeth.de>
In-Reply-To: <87zkrz314j.fsf@SSpaeth.de>
OpenPGP: id=D21739E9
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature";
	boundary="------------enigEC6DAF75E244C68ABEE1ADE9"
Precedence: list
Reply-To: notmuch <notmuch@notmuchmail.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigEC6DAF75E244C68ABEE1ADE9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 12/21/2010 04:51 AM, Sebastian Spaeth wrote:
> So what am I doing wrong, I pulled your branch and compiled/installed,
> but I don't see any signature verification in my emacs?
>=20
> Unless all work is still in the notmuch binary,=20

yes, the branch as it stands just concerns itself with the notmuch binary=
=2E

> I see for your mail,
> e.g.=20
> "sigstatus": [{"status": "error","keyid": "ED34CEABE27BAABC", "errors":=

> 2}]
> (perhaps due to me not having your key???)

yup, that is why you get that error.

> On a side note:
> notmuch show format=3Djson --verify id:"87aak08fu8.fsf@servo.finestruct=
ure.net"
>=20
> is ok but:
> notmuch show --verify id:"87aak08fu8.fsf@servo.finestructure.net"
>=20
> neither omplains nor shows anything in addition. Should it do one of th=
e
> two?

the patch is specifically only for the json output.  If you'd like the
same features for the non-json output, that would be cool to see, but i
don't understand those formats well enough to know how to incude that
kind of info in them.

If this seems like i've only done one small corner of the task needed to
get signature verification: you're right!  I deliberately scoped the
initial task to be small-but-doable.  i want to make sure this seems
acceptable/reasonable before digging into the other pieces.

	--dkg


--------------enigEC6DAF75E244C68ABEE1ADE9
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/

iQIcBAEBCgAGBQJNEMl8AAoJEMzS7ZTSFznpDRwQAKWPuvfF1LegNfCWbJcTRUJL
Cdn7NljH3HsEYpXixODcWIuvg8nilSLXqII941bflvJprCTI79ktw3/VlgMuhdS9
cQjC0qdze8ePgmYJGZJdNengTSmNrytb1dfW/Y9UHVrco+DZp/fEV5g5W6Rwbenb
6IkmfsXZvPrhCe/JajkY4Lfajkl6R55qsnaq2QklPHrvs2T5rMbyNQBKvIQmu9qM
e1TJUt2J8vKRiWd5yL2H4mATS4LErUUo2Y1rbQiYGvuUy2QKjO4qiOindmnWTlY0
qSdCRvK6ciP5nfAZMjF6xsZMahQ6HwA428fI39cCl7UdiKnbOgS9kJZZZ/Cm7MJu
GNDoM0U7hvYZ5xbLj4U2WyMjT1a3NHhSRA0mbCEm9Sfppp3K9JJDhceyGIRXCCf/
EXF1WH9xwPkuEf+Hzzy7hQxDoUAdZGFHNYWYFF1Kbx7Tzh9tpNmV/hb8l9g9hzoT
LMrvKj+Ria4mVITs12ZqJJqqFqqhSJqe5bppW3IRiuAQrIPw/tf3R1z4ZeeI6L9R
SwRmFh3EACeduGqWH92Q9/N3MDLQ6VpAU6+/CGWehNvLqjNj5gVNNtqxtyWNfJoh
CnHD813pmJmYdeMionCZi2ukE0taHi57acYhjdi3JEAiw0RZulj0YRDRoNXT8z9a
dPvnHwzklFMyWMwpG7w4
=oRex
-----END PGP SIGNATURE-----

--------------enigEC6DAF75E244C68ABEE1ADE9--