Re: [keyassure] publishing the public key

Yaron Sheffer <yaronf.ietf@gmail.com> Tue, 15 February 2011 18:17 UTC

Return-Path: <yaronf.ietf@gmail.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 16B953A6D2A for <keyassure@core3.amsl.com>; Tue, 15 Feb 2011 10:17:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.19
X-Spam-Level:
X-Spam-Status: No, score=-101.19 tagged_above=-999 required=5 tests=[AWL=0.449, BAYES_00=-2.599, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_DNSWL_LOW=-1, 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 vu841jTX0+9P for <keyassure@core3.amsl.com>; Tue, 15 Feb 2011 10:17:51 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 0AE533A6D33 for <keyassure@ietf.org>; Tue, 15 Feb 2011 10:17:50 -0800 (PST)
Received: by fxm9 with SMTP id 9so563602fxm.31 for <keyassure@ietf.org>; Tue, 15 Feb 2011 10:18:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=MMqfNWD694h+ojtvtC/Rf5+2lA1tyegXohHyV2247ng=; b=uVwMRMhiSxSv52rMfM3ustRkV7tpae5gXOJq7vK9JIhgDHdQtpexBr0I3RKyXWQfcg Au2iSyIuPCQqHQRm/amVxWlPCxVosmMovYsRVzZEljkQ3xzu/LPxubTPNFNtB/hFw9jV LzNxgZ6JONfLUBMac0PFJPRm5LlxydYT4FAGU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=NIqpHPUZa+318Ui1JJUPU+eUIswv0mjarZ03sz7XOKayT0YKZECDIEAvQ7F72zMuiO PCi1gJTNoFYW4lM55gfJfdvzwPXgrk8jzIGKiru24kdBK868ydfNoUsReww+sm6ChNKu pBmoyrNnkA2G2SXN/DF+avBKOaPA0FVAApmHE=
Received: by 10.223.74.206 with SMTP id v14mr6536668faj.66.1297793887793; Tue, 15 Feb 2011 10:18:07 -0800 (PST)
Received: from [10.0.0.1] (bzq-79-179-49-128.red.bezeqint.net [79.179.49.128]) by mx.google.com with ESMTPS id n3sm1813123fax.7.2011.02.15.10.18.06 (version=SSLv3 cipher=OTHER); Tue, 15 Feb 2011 10:18:07 -0800 (PST)
Message-ID: <4D5AC35C.3010807@gmail.com>
Date: Tue, 15 Feb 2011 20:18:04 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: keyassure@ietf.org
References: <mailman.3010.1297769546.4701.keyassure@ietf.org>
In-Reply-To: <mailman.3010.1297769546.4701.keyassure@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Tue, 15 Feb 2011 18:17:52 -0000

Just for the record, IKEv2 does support bare public keys (though I don't 
think they are often used).

The exact RFC 5996 wording regarding the format is:

"Raw RSA Key" contains a PKCS #1 encoded RSA key, that is, a DER-encoded RSAPublicKey structure (see [RSA  <http://tools.ietf.org/html/rfc5996#ref-RSA>] and [PKCS1  <http://tools.ietf.org/html/rfc5996#ref-PKCS1>]).


Yes, it's ASN.1, but it's well defined. Let's not forget that there have 
been security vulnerabilities related to the on-the-wire format of pubic 
keys in the past.

Thanks,
     Yaron
> Message: 4
> Date: Mon, 14 Feb 2011 18:35:23 -0800
> From: Paul Hoffman<paul.hoffman@vpnc.org>
> Subject: Re: [keyassure] Issue #14 - publishing the public key
> To: keyassure@ietf.org
> Message-ID:<4D59E66B.1090808@vpnc.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Personally, I don't see much use for bare public keys, but I hear that
> many people do, and I don't see much harm in adding them.
>
> However, if the WG wants to add them, I would want to see some wording
> for how the on-the-wire format would look. That is, you can't just put
> the bits of the public key there: you also have to say what the
> signature algorithm is and, if the algorithm requires parameters, what
> the parameters are.
>
> Any of the folks who seem most in favor of this: please suggest some
> wording here. You need to say what the format is and how the TLS client
> would compare the value gotten from the TLSA RR with the certificate
> they get in the TLS handshake.