Re: [keyassure] publishing the public key

Stephen Kent <kent@bbn.com> Wed, 23 February 2011 01:19 UTC

Return-Path: <kent@bbn.com>
X-Original-To: keyassure@core3.amsl.com
Delivered-To: keyassure@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2337A3A6768 for <keyassure@core3.amsl.com>; Tue, 22 Feb 2011 17:19:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.536
X-Spam-Level:
X-Spam-Status: No, score=-102.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 vdd-2Ih7d1Ck for <keyassure@core3.amsl.com>; Tue, 22 Feb 2011 17:19:20 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id AD0B03A672F for <keyassure@ietf.org>; Tue, 22 Feb 2011 17:19:20 -0800 (PST)
Received: from dommiel.bbn.com ([192.1.122.15]:58581 helo=[169.223.137.111]) by smtp.bbn.com with esmtp (Exim 4.74 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1Ps3Od-000DsG-UJ; Tue, 22 Feb 2011 20:20:04 -0500
Mime-Version: 1.0
Message-Id: <p06240803c98a0b49a5f9@[169.223.137.111]>
In-Reply-To: <B6315D18-AE32-4CE8-A7A5-7D155C1F259B@bblfish.net>
References: <E1PqbpT-0000pd-Kz@login01.fos.auckland.ac.nz> <alpine.LFD.1.10.1102201747370.26752@newtla.xelerance.com> <4D619C94.8090702@vpnc.org> <93E9FABD-A84A-4A4E-AF96-6E101604F8B4@bblfish.net> <p06240803c98892e88fc4@[59.188.192.152]> <1FAB667F-44F9-4349-B11B-F4FECD51BB81@bblfish.net> <p06240804c988c84933b6@[169.223.137.111]> <B6315D18-AE32-4CE8-A7A5-7D155C1F259B@bblfish.net>
Date: Tue, 22 Feb 2011 19:56:55 -0500
To: Henry Story <henry.story@bblfish.net>
From: Stephen Kent <kent@bbn.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: WebID Incubator Group WG <public-xg-webid@w3.org>, keyassure@ietf.org
Subject: Re: [keyassure] publishing the public key
X-BeenThere: keyassure@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Key Assurance With DNSSEC <keyassure.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/keyassure>
List-Post: <mailto:keyassure@ietf.org>
List-Help: <mailto:keyassure-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2011 01:19:22 -0000

At 10:17 AM +0100 2/22/11, Henry Story wrote:
>...
>  >
>>  I don't think that most users, who often can't even tell if they 
>>have contacted a TLS-secured site, would think of a public key as 
>>part of the identity for the service. I also don't think that most 
>>of them think about the port either.
>
>I was not speaking to most users but to this group of security 
>specialists during a discussion on a protocol. The public key is a 
>definite description that uniquely identifies the agent for the 
>purpose of computers, not for the general public.

The context you envisioned was not clear from your statement. a 
public key can be a UID for an object, but I'd hesitate to call it 
descriptive.

>...
>
>I am aware of symmetric cryptography's role. But it is public key 
>cryptography that is core in authenticating the server, and setting 
>up the symmetric crypto channel. Symmetric cryptography is used 
>because it is less cpu intensive.

I think it best to be precise when discussing what one would like
to see become a standard.

Steve