IETF Logo Mail Archive

Re: [keyassure] publishing the public key

Paul Wouters <paul@xelerance.com> Tue, 15 February 2011 22:30 UTC

Return-Path: <paul@xelerance.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 29B4B3A6DE3 for <keyassure@core3.amsl.com>; Tue, 15 Feb 2011 14:30:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 XpcGWcVEE81O for <keyassure@core3.amsl.com>; Tue, 15 Feb 2011 14:30:54 -0800 (PST)
Received: from newtla.xelerance.com (newtla.xelerance.com [193.110.157.143]) by core3.amsl.com (Postfix) with ESMTP id 238663A6D7C for <keyassure@ietf.org>; Tue, 15 Feb 2011 14:30:54 -0800 (PST)
Received: from tla.xelerance.com (tla.xelerance.com [193.110.157.130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by newtla.xelerance.com (Postfix) with ESMTP id 4818FC57C; Tue, 15 Feb 2011 17:31:19 -0500 (EST)
Date: Tue, 15 Feb 2011 17:31:18 -0500
From: Paul Wouters <paul@xelerance.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
In-Reply-To: <4D5AC35C.3010807@gmail.com>
Message-ID: <alpine.LFD.1.10.1102151729130.3131@newtla.xelerance.com>
References: <mailman.3010.1297769546.4701.keyassure@ietf.org> <4D5AC35C.3010807@gmail.com>
User-Agent: Alpine 1.10 (LFD 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: 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: Tue, 15 Feb 2011 22:30:55 -0000

On Tue, 15 Feb 2011, Yaron Sheffer wrote:

> 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.

Openswan (IPsec for Linux) supports raw RSA keys for IKEv1 and IKEv2.

Paul

v2.23.0 | Report a Bug | By Email