IETF Logo Mail Archive

[perpass] Fwd: PRISM-Proof Email, Key Management and Publication Specification

Phillip Hallam-Baker <hallam@gmail.com> Thu, 17 October 2013 23:27 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0BFF11E8195 for <perpass@ietfa.amsl.com>; Thu, 17 Oct 2013 16:27:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.592
X-Spam-Level:
X-Spam-Status: No, score=-2.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 HGbroEsRfpbn for <perpass@ietfa.amsl.com>; Thu, 17 Oct 2013 16:27:45 -0700 (PDT)
Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id A2B2E11E81F0 for <perpass@ietf.org>; Thu, 17 Oct 2013 16:27:41 -0700 (PDT)
Received: by mail-la0-f49.google.com with SMTP id ev20so82621lab.8 for <perpass@ietf.org>; Thu, 17 Oct 2013 16:27:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=iSpATh1+xaHPpxnWuFuAtcXA6A/Wf/vbbRbtYEdbrZY=; b=Bd/w0q6PzXLnF1mIQXAHvcAEqXe5+Ca2t6bGVm6uxHIWCcLpUUp+4ubUZIF1Jlj/qV dwzu9b68WRwyiVt2+smnFs+24MGLQ8/9Nmh5aiauNOyX3BHTFxu0XrwlBOyX9W+fTf7Y RB+AffymY57N3woThMCOQGdzzHkKBZQSmFZBxJTqkcHK1effB1hzEDtjIuEx9ooJ6cuk A2aItYSpQHeEfO/xhJWpouhVz7gMhnUHByIAtK7aDoT7H6nVlF3vDyqlLUGIysGo/G+Q fzHqZv18bOXv67Qjgp5a9FKNFU797cGtJWyNIy9vF8R8KYPS4hkwtlERQuRID1uZnuhq YtuQ==
MIME-Version: 1.0
X-Received: by 10.152.9.194 with SMTP id c2mr77559lab.83.1382052460528; Thu, 17 Oct 2013 16:27:40 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Thu, 17 Oct 2013 16:27:40 -0700 (PDT)
In-Reply-To: <CAMm+LwioSoi-UXnDQy3+tL6sFcoC_MoGTDtOcDXJGXEZqQ=yDA@mail.gmail.com>
References: <CAMm+LwioSoi-UXnDQy3+tL6sFcoC_MoGTDtOcDXJGXEZqQ=yDA@mail.gmail.com>
Date: Thu, 17 Oct 2013 19:27:40 -0400
Message-ID: <CAMm+LwjH86U2Lb4t4T558GiaM-UPLA1hReZB6n1VUGE+_hCW0g@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: perpass <perpass@ietf.org>
Content-Type: multipart/alternative; boundary="001a1133dba0f8874e04e8f8298b"
Subject: [perpass] Fwd: PRISM-Proof Email, Key Management and Publication Specification
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The perpass list is for discussion of the privacy properties of IETF protocols and concrete ways in which those could be improved. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Oct 2013 23:27:46 -0000

[Try #2]

I have produced a first draft of the specification for the Key Publication
service and key management tool that talks to it.

The code being documented is rough. Not least because the ASN.1 encoder I
wrote does not know about ASN.1 inanities like OPTIONAL, IMPLICIT or such
yet so the certs are not DER encoded.

http://tools.ietf.org/html/draft-hallambaker-prismproof-key-00


This specification represents one of the two interfaces to the blob in the
cloud that I call 'research'. We don't yet know the best approach to trust
management but it is going to be a lot easier to find out if we separate
that hard research problem from the 'plumbing' required to make secure
email work.

The other interface is the Omnibroker specification I wrote earlier this
year.

http://tools.ietf.org/html/draft-hallambaker-httpsession-01
http://tools.ietf.org/html/draft-hallambaker-wsconnect-04
http://tools.ietf.org/html/draft-hallambaker-omnibroker-06


I believe that between these specifications we have a fairly complete idea
of what the 'plumbing' side of 'Privacy Protected' Email should look like.

The Strong Email Addresses shown earlier provide a demonstration that we
can solve this problem for at least some class of email user using stock
email clients (OK plus a proxy gateway to send the mail).

If people would like to write code, we are at the point where that is now
practical. In addition it would be very useful if people could find out
information such as how various commonly used email clients store S/MIMe
keys and how might a program do the user's job of configuration for them.

-- 
Website: http://hallambaker.com/



-- 
Website: http://hallambaker.com/

v2.23.0 | Report a Bug | By Email