Re: not really pgp signing in van

Ted Lemon <Ted.Lemon@nominum.com> Tue, 10 September 2013 01:42 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF1C611E817C for <ietf@ietfa.amsl.com>; Mon, 9 Sep 2013 18:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.473
X-Spam-Level:
X-Spam-Status: No, score=-106.473 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GMSs03Vu-CQJ for <ietf@ietfa.amsl.com>; Mon, 9 Sep 2013 18:42:11 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id 23F4811E817E for <ietf@ietf.org>; Mon, 9 Sep 2013 18:42:10 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKUi548l6GajMJHNV7nfuVfLuceIv3xHjE@postini.com; Mon, 09 Sep 2013 18:42:11 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id BAEA11B823A for <ietf@ietf.org>; Mon, 9 Sep 2013 18:41:56 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id B3B5719006D; Mon, 9 Sep 2013 18:41:56 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 9 Sep 2013 18:41:56 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: John R Levine <johnl@taugh.com>
Subject: Re: not really pgp signing in van
Thread-Topic: not really pgp signing in van
Thread-Index: AQHOqpqEB3VH/4NMm0OmqkHjUm9ALJm5aiMAgABaqYD//9WJAIAARlSA///KM4CAAFZ3gIAC1QGAgAAEoYCAAPmWgIAAFPEAgABoNQCAAAGxAIAAFfqAgAAJL4CAADHKgIAAAaIAgAADyACAAARAgA==
Date: Tue, 10 Sep 2013 01:41:55 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077527E488@mbx-01.win.nominum.com>
References: <20130910010719.33978.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B63077527E234@mbx-01.win.nominum.com> <alpine.BSF.2.00.1309092125360.34090@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1309092125360.34090@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <AF5BE001E39DCB4CBC0E3BFE28E4347B@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2013 01:42:18 -0000

On Sep 9, 2013, at 9:26 PM, John R Levine <johnl@taugh.com> wrote:
> Um, didn't this start out as a discussion about how we should try to get
> people using crypto, rather than demanding perfection that will never
> happen?

Yes.

> Typical S/MIME keys are issued by CAs that verify them by
> sending you mail with a link.  While it is easy to imagine ways that
> could be subverted, in practice I've never seen it.

The most obvious way that it can be subverted is that the CA issues you a key pair and gives a copy of the private key to one or more others who would like either to be able to pretend to be you, or to intercept communication that you have encrypted.   I would argue that this is substantially less trustworthy than a PGP key!

Of course you can _do_ S/MIME with a non-shared key, but not for free, and not without privacy implications.   (I'm just assuming that an individual can get an S/MIME Cert on a self-generated public key—I haven't actually found a CA who offers that service.)

> Same issue.  I can send signed mail to a buttload more people with
> S/MIME than I can with PGP, because I have their keys in my MUA.
> Hypothetically, one of them might be bogus.  Realistically, they aren't.

Very nearly that same degree of assurance can be obtained with PGP; the difference is that we don't have a ready system for making it happen.

E.g., if my MUA grabs a copy of your key from a URL where you've published it, and validates email from you for a while, it could develop a degree of confidence in your key without requiring an external CA, and without that CA having a copy of your private key.   Or it could just do ssh-style leap-of-faith authentication of the key the first time it sees it; a fake key would be quickly detected unless your attacker controls your home MTA or the attacked identity's home MTA.