Re: [pkng] Where to go? What to do?

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Fri, 01 October 2010 20:25 UTC

Return-Path: <dkg@fifthhorseman.net>
X-Original-To: pkng@core3.amsl.com
Delivered-To: pkng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56DFB3A6E2A for <pkng@core3.amsl.com>; Fri, 1 Oct 2010 13:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.058
X-Spam-Level:
X-Spam-Status: No, score=-3.058 tagged_above=-999 required=5 tests=[AWL=-0.542, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, URIBL_RHS_DOB=1.083]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wU1YEVQeFt4M for <pkng@core3.amsl.com>; Fri, 1 Oct 2010 13:25:05 -0700 (PDT)
Received: from relay00.pair.com (relay00.pair.com [209.68.5.9]) by core3.amsl.com (Postfix) with SMTP id 13E3A3A6CA0 for <pkng@irtf.org>; Fri, 1 Oct 2010 13:25:05 -0700 (PDT)
Received: (qmail 22535 invoked from network); 1 Oct 2010 20:25:49 -0000
Received: from 216.254.70.154 (HELO ?192.168.23.207?) (216.254.70.154) by relay00.pair.com with SMTP; 1 Oct 2010 20:25:49 -0000
X-pair-Authenticated: 216.254.70.154
Message-ID: <4CA643C9.9040509@fifthhorseman.net>
Date: Fri, 01 Oct 2010 16:25:45 -0400
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.9) Gecko/20100918 Icedove/3.1.4
MIME-Version: 1.0
To: Massimiliano Pala <Massimiliano.Pala@Dartmouth.edu>
References: <p06240825c8c7fd5ca338@[10.20.30.163]> <4CA63F67.4010101@Dartmouth.edu>
In-Reply-To: <4CA63F67.4010101@Dartmouth.edu>
X-Enigmail-Version: 1.1.2
OpenPGP: id=D21739E9
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="------------enig29E933E131D6DCCD200D0FC0"
Cc: pkng@irtf.org
Subject: Re: [pkng] Where to go? What to do?
X-BeenThere: pkng@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Public Key Next Generation \(PKNG\) Research Group" <pkng.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/pkng>, <mailto:pkng-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/pkng>
List-Post: <mailto:pkng@irtf.org>
List-Help: <mailto:pkng-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/pkng>, <mailto:pkng-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Oct 2010 20:25:06 -0000

On 10/01/2010 04:07 PM, Massimiliano Pala wrote:

> most important issues we face today (let me know if you need a copy):
> 
>   http://portal.acm.org/citation.cfm?id=1750389.1750404

i'd be interested in a copy of this paper.

> My idea would be to provide two documents. The first describing the overall
> infrastructure and the PKS distributed protocol. This is the protocol that
> would allow PKI-to-PKI interactions via a distributed P2P overlay network.

Though we most likely aren't using the protocols you describe (we're not
even relying on X.509), we actually already have something like this up
and running.  The Monkeysphere project (http://web.monkeysphere.info/ --
i'm one of the developers) uses the P2P SKS keyserver network to
distribute OpenPGP certificates, which are in turn used to authenticate
netork peers (primarily HTTPS and SSH at the moment).

We treat any existing X.509 certificates as raw carriers for public key
material, and authenticate the material through the OpenPGP Web of
Trust.  This means using the same PKI (the WoT) for mail, web browsing,
and SSH, which means we have the potential for intuitive UI
consolidation that humans might be able to understand.

It also means that multiple authorities can choose to certify the same
entity, which breaks one of the big stumbling blocks in the way the
X.509 arrangement is currently set up.  (single-certifier certificates
cause CA lock-in for many parties; CA lock-in dramatically increases the
risk of compromise of authenticated networked communications).

I (and the rest of the Monkeysphere team) would welcome any criticisms,
suggestions, or concerns you have about this project.  The system is
already in use, and we hope to see it grow healthily.

Regards,

	--dkg