Message-ID: <4CF15D67.1070904@fifthhorseman.net>
Date: Sat, 27 Nov 2010 14:35:03 -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: PGP/MIME signature verification
OpenPGP: id=D21739E9
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature";
	boundary="------------enig9659FA14D89BBA62DEF020C0"
Precedence: list
Reply-To: notmuch <notmuch@notmuchmail.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9659FA14D89BBA62DEF020C0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

hey folks--

the signature-verification branch on my git repo [0] contains functional
PGP/MIME signature verification if you supply the --verify argument to

 notmuch show --format=3Djson

It relies on gpg being in the path, and on the user having the signer's
key in their gnupg keyring.

The patchset depends on the MIME reorganization produced initially by
dme (and rebased against 0.5 in my mp3-on-0.5 branch).

the emacs frontend doesn't yet know how to deal with the resultant data,
so the signature verification doesn't reach the user yet.

The JSON this change produces is similar (but not identical) to my
earlier proposal on this list.

In particular, the parent MIME part (content-type: multipart/signed) is
what gets the sigstatus object, which is itself a list of signature
objects, like this:

"sigstatus": [
 {
  "created": 1290557507,
  "fingerprint": "0EE5BE979282D80B9F7540F1CCD2ED94D21739E9",
  "status": "good"
 },
 {
  "keyid": "DEADBEEFDECAFBAD",
  "status": "bad"
 }
]

(this example shows a mime part signed by two keys, the signature from
one checking out properly, and the signature from the other failing --
most multipart/signed MIME parts will only be signed by one party)

I'd appreciate any feedback people have on the change, and any
suggestions on how to integrate its results into the emacs interface.

Also, i'm curious what i can do to make these changes more acceptable
for the mainline.  should i rebase them against mainline master?  or
demonstrate a functional merge?  i'm new to how this community likes to
use git, so pointers to suggested approaches would be welcome.

I should also note that in the course of pursuing this, i found that
GMime's upstream author is very receptive to suggestions and feedback
about crypto.  If anyone else in the notmuch community wants to make
suggestions about what we might need for future extensions in this
direction, he's probably a good resource to help us get there.

Regards,

	--dkg

[0] git://lair.fifthhorseman.net/~dkg/notmuch


--------------enig9659FA14D89BBA62DEF020C0
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/

iQIcBAEBCgAGBQJM8V1nAAoJEMzS7ZTSFznpRYoP/RWLtozm6Nh3HB1vA+Hk1tFl
YtPdzbSu3masLY6QHViNckowp1l5SzAfIKBssbZUXH2J6Fj7492JVm49sb0LmPdp
33ZX8XojD/PGJH3kthpGTCyhYg6w6XqmDiviYiF+66w8eiZefl4lhvzahxoARvkz
k7yp53u9l4vbJB+ac/++EbyfvwdfyxR8voyex5a6aRAA68OBRV6ut11pa7+eagzw
fCEL1QzMEJKYfvsQ9OlHo6g9bbK6N5lTKWgjo9eKTMFRx6hE5YPBC8sZOdEYZDtv
MyliQp1AWEnYQYiOu5BK3+w7la4nvOpBuuu9dHR9uSRLBxGMvFV+asuG/HNz0HmV
Z4PMFVnj/8PVd52yZKwdsy0MtOJZHJNuB8x4WYdtbriebnnAa55MUCCkFOBeQdrz
7xo4jHwhHA+/kLYa44vZzsDQNllzGMbaARrrMP8cWQ/3YjVSi0Rs7+Nu9OLjn4X4
Q3pmDp08m569Ct3m6jsiB/O+IHHosunPjqYbZuRXFoANZg4qjxvEoev4GnMjRozg
pBUxSWXCXCKa89iGj7uzhboDILpwgyVSBS8xfhn+Px56x/17mefC+XqAfwoJW7mI
4wBoOOtSTdDIexzAkWITQZoo5DzdBaWaq/LSBZnfZMDKpo+iaiFc6rwfB91QRL/u
82ReY28t/BqeHD0qAqTh
=1wrH
-----END PGP SIGNATURE-----

--------------enig9659FA14D89BBA62DEF020C0--