IETF Logo Mail Archive

Re: [keyassure] publishing the public key

Yaron Sheffer <yaronf.ietf@gmail.com> Tue, 15 February 2011 19:42 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 34B893A6C32 for <keyassure@core3.amsl.com>; Tue, 15 Feb 2011 11:42:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.227
X-Spam-Level:
X-Spam-Status: No, score=-102.227 tagged_above=-999 required=5 tests=[AWL=1.373, BAYES_00=-2.599, 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 uBs8lIqgKbYv for <keyassure@core3.amsl.com>; Tue, 15 Feb 2011 11:42:05 -0800 (PST)
Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by core3.amsl.com (Postfix) with ESMTP id C6C5B3A6D69 for <keyassure@ietf.org>; Tue, 15 Feb 2011 11:42:04 -0800 (PST)
Received: by bwz12 with SMTP id 12so854758bwz.27 for <keyassure@ietf.org>; Tue, 15 Feb 2011 11:42:29 -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 :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=U0qatTzIA41gGYo69wrLSpwqwpb7KSGyYHgAcSoaA/0=; b=dANqz4WwjiHZL2MhZkyRFTVtwd5xXkmJbrMsB1/vyf14uqA1OYxIt8karBM6Sr5Z2Z ns0WCPXamFj+C/6HeYcvzV213V/y+WwGR3OubVSjWwf8y7N2DkQ3ER2gvlpOi1y11OJM cfrTCFXAYolvFalv8a+D2N8YThZxEyPlkLV1M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=rTW5KJq5buvCTa/NjHebocPlrMKJ5r/m0GwDiBLUF+jebNa0VR9OV0YYtezY5hi1g0 RVIQsBfZnhUjf2T4xzKX/B+93e6ZMNMi+hVM25/VH1Q9lUuicWeT+fjrIAuqFNF3P6dS bP3JtvVQoO0x5ryk8s3HmkdGnsK8fdQ9I5cT4=
Received: by 10.204.55.65 with SMTP id t1mr9191028bkg.140.1297798948219; Tue, 15 Feb 2011 11:42:28 -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 x38sm2865478bkj.1.2011.02.15.11.42.24 (version=SSLv3 cipher=OTHER); Tue, 15 Feb 2011 11:42:26 -0800 (PST)
Message-ID: <4D5AD71D.1080105@gmail.com>
Date: Tue, 15 Feb 2011 21:42:21 +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: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
References: <mailman.3010.1297769546.4701.keyassure@ietf.org> <4D5AC35C.3010807@gmail.com> <20110215190718.GA24175@LK-Perkele-VI.localdomain>
In-Reply-To: <20110215190718.GA24175@LK-Perkele-VI.localdomain>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
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 19:42:06 -0000

Hi Ilari,

What I had in mind was this padding attack: 
http://www.openssl.org/news/secadv_20030319.txt

Thanks,
     Yaron

On 02/15/2011 09:07 PM, Ilari Liusvaara wrote:
> On Tue, Feb 15, 2011 at 08:18:04PM +0200, Yaron Sheffer wrote:
> >
> > 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.
>
> Letting factors outside the signed blocks interfere with interpretation
> of stuff inside signature? Signed blocks with multiple interpretations?
>
> What else? Got summary of some of the issues (just for reference, quick
> googling doesn't yield anything relvant)?
>
> -Ilari

v2.23.0 | Report a Bug | By Email