Message-ID: <4D6BF0AA.3070706@fifthhorseman.net>
Date: Mon, 28 Feb 2011 13:59:54 -0500
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.2.13) Gecko/20101213 Icedove/3.1.7
MIME-Version: 1.0
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: [Review] Re: new "crypto" branch providing full PGP/MIME support
References: <4CF15D67.1070904@fifthhorseman.net>
	<87aak08fu8.fsf@servo.finestructure.net>
	<87fwsf9mip.fsf@servo.finestructure.net>
	<87tygl29vu.fsf@servo.finestructure.net>	<87oc5yi9us.fsf@zancas.localnet>
	<87d3mdvjwz.fsf@bookbinder.fernseed.info>	<87k4gk70ng.fsf@SSpaeth.de>
	<87sjv8i7v6.fsf@irigaray.ross.mayfirst.org>
	<87sjv86mp9.fsf@servo.finestructure.net>
In-Reply-To: <87sjv86mp9.fsf@servo.finestructure.net>
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature";
	boundary="------------enigFEC2910BDA0AF6F7C922CB84"
Precedence: list
Reply-To: notmuch <notmuch@notmuchmail.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigFEC2910BDA0AF6F7C922CB84
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 02/28/2011 01:25 PM, Jameson Rollins wrote:
> On Mon, 28 Feb 2011 08:52:45 -0500, Ross Glover <ross@ross.mayfirst.org=
> wrote:
>> I too am now running the crypto branch and find it quite amazing.  The=

>> one feature I would like added, though, is some face color or
>> auto-tagging in the search buffer for mail with encrypted mime parts.
>> It seems like this could be achieved with notmuch effort (by someone
>> notme) by adding similar functionality to that of attachments in
>> index.cc.
>=20
> Yes, this is a good idea, Ross, and one that I've actually been wanting=

> to implement.  I was thinking of auto-tagging messages with signed part=
s
> with something like "signed", and encrypted messages with "encrypted".
> Do people like those tags, or would they prefer to see something
> different?  Or more specific, like "pgp-signed"?

i don't care much about the difference between PGP/MIME and S/MIME
message formats, so i prefer the term "signed" to "pgp-signed" and
"encrypted" to "pgp-encrypted".

  ----

But: what does the "signed" tag mean? i wouldn't want to necessarily
conflate these four ideas:

 0) "this message claims to be cryptographically-signed"

 1) "we have verified a cryptographic signature over this message"

 2) "we have verified a cryptographic signature over this message from a
known key (that is, we believe we know who the key belongs to)"

 3) "we have verified a cryptographic signature on this message from the
sender claimed in the From: line"

3 implies 2, 2 implies 1, and 1 implies 0, of course.  But which level
would a "signed" tag signify?

I'll also note that signed+encrypted messages would not get tagged with
"signed" unless the recipient has successfully decrypted them.  And
then, it's possible that some sub-parts of a message are signed, and
others are not.  Would the tags indicate the maximum "level" found? or
the minimum?  something else?

  ----

For that matter, what would an automatically-placed "encrypted" tag
mean?  i can think of a few different approaches:

 0) some part of this message is wrapped in an encrypted MIME block

 1) some part of this message is wrapped in an encrypted MIME block that
claims to be decryptable by a key you control

 2) some part of this message is wrapped in an encrypted MIME block and
you can actually decrypt it (have decrypted it in the past?).

2 in particular couldn't be auto-assigned without having access to the
user's secret key material in the first place, but maybe it could be
assigned after a decryption succeeds?


	--dkg


--------------enigFEC2910BDA0AF6F7C922CB84
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/

iQJ8BAEBCgBmBQJNa/CqXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwRUU1QkU5NzkyODJEODBCOUY3NTQwRjFD
Q0QyRUQ5NEQyMTczOUU5AAoJEMzS7ZTSFznpBvsP/iC8w4MQm7RCzTnR0C/C17lH
OcyWPN7T/hiDG9SvdtFOSVHfFZLYGP22bxzey4SuAXoh6wQwRjfB9YeR0x7g9WHG
tiDH6a6yLMWymj26RuLYN47Q0TLwQRdM9KMVq+c8YuNxMO4f0X88Pi87vz8Fl8La
2q64X2mGMqp5YWlL6jaiC02PHxQFFLtTMZQNmb5n6OIdbrYC365sRcZ4jbFxywfq
PZEDflgIsKG3DaDwCGegPM58ndnqKlsq1HfNlKlGkLDAiEsxx+MJT67thgSmmyJe
05QwTwSnY2WDVlDu5BR9BU3/uD/bBuyGCjykblwYZhTACRObWQUdI8IG+VF/HQ2y
ZJcKIeRlS33A5mx6X8i+0anvNNsN3YXcd4CzqIuc/haWw9xrNPhvklSqQwgJC/d3
OUbP996q0Yjy/3Rkw4BmOhmYF49cF9SMxVox56CURI2MIwWxQ2Cv7aMwPR9VU7cy
LKHPgLODOfgT6o72BgE0CAoNqlHFjFLV2PSipQpcjAxwIC7v1retTphZuVCWqXdM
txhVp/58swMqhJ2s0Jyf0ryOrCELSQSZOR/LsAZHWmG5/LLI/4934XGVaY3A+8Uy
oieo3jHCiy3zYlaopJNHP65cZQ6XLhagOyVwz8/UwZjgjtnMTZa6CRe8fehXqNzd
Un4ZKeCWP09CLEEHJ5VC
=xybu
-----END PGP SIGNATURE-----

--------------enigFEC2910BDA0AF6F7C922CB84--