IETF Logo Mail Archive

Re: [TLS] RFC-4366-bis and the unrecognized_name(112) alert

Michael D'Errico <mike-list@pobox.com> Wed, 09 June 2010 17:16 UTC

Return-Path: <mike-list@pobox.com>
X-Original-To: tls@core3.amsl.com
Delivered-To: tls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 08D393A69AD for <tls@core3.amsl.com>; Wed, 9 Jun 2010 10:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.707
X-Spam-Level:
X-Spam-Status: No, score=-1.707 tagged_above=-999 required=5 tests=[AWL=0.892, 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 vZV2NaysXDgf for <tls@core3.amsl.com>; Wed, 9 Jun 2010 10:16:46 -0700 (PDT)
Received: from sasl.smtp.pobox.com (a-pb-sasl-quonix.pobox.com [208.72.237.25]) by core3.amsl.com (Postfix) with ESMTP id 305AF3A6994 for <tls@ietf.org>; Wed, 9 Jun 2010 10:16:46 -0700 (PDT)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTP id E9689BAC88; Wed, 9 Jun 2010 13:16:47 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=sasl; bh=SgzdFgcD3Hd6 tNXY79gsxInRZ6A=; b=U8j5Zana49d4ayBPFc8Gve23RJiYddHA9vZ5Ugy1j/ra PAqhShh8LQcopPV4A0afgder69KWjuvmDE5e63C9+NyyrCKlPKpUF2/38TnIzXmg DamQJ+An7+U4bsQglXcPC/ykff4LX26s21vnJUXAdDIi5njl6io5QBAXBJmgeBo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=sasl; b=EyJ1FT rEMqYB3Xe15RY5t/PyzRtRv0Jhq7943y7IL89KpOXQIzkeLuIF1Fxfq3X5vu/EGD RSP7e/JZmluKbikrE7QapEn8lIN2WIES8VaSm3owmrGzMQkoFDck92ukhbfV/cbS vHuMdskjWsgxqYWMx2xr7hfoUm1N57sK3yMDc=
Received: from a-pb-sasl-quonix. (unknown [127.0.0.1]) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTP id C44FBBAC86; Wed, 9 Jun 2010 13:16:45 -0400 (EDT)
Received: from administrators-macbook-pro.local (unknown [24.234.114.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTPSA id 96503BAC85; Wed, 9 Jun 2010 13:16:42 -0400 (EDT)
Message-ID: <4C0FCC79.9010204@pobox.com>
Date: Wed, 09 Jun 2010 10:16:41 -0700
From: Michael D'Errico <mike-list@pobox.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
References: <4C0FA538.7050309@pobox.com> from "Michael D'Errico" at Jun 9, 10 07:29:12 am <201006091456.o59EukJ3015376@fs4113.wdf.sap.corp> <AC1CFD94F59A264488DC2BEC3E890DE50AA7E552@xmb-sjc-225.amer.cisco.com> <p0624083bc83572582a36@[10.20.30.158]>
In-Reply-To: <p0624083bc83572582a36@[10.20.30.158]>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: C7E5F022-73EA-11DF-872C-6730EE7EF46B-38729857!a-pb-sasl-quonix.pobox.com
Cc: tls@ietf.org
Subject: Re: [TLS] RFC-4366-bis and the unrecognized_name(112) alert
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jun 2010 17:16:47 -0000

Paul Hoffman wrote:
> 
> ... there is still not enough definitive wording. I propose:
> 
> The ServerNameList MUST NOT contain more than one name of the same
> name_type.  If the server understood the ClientHello extension but
> does not recognize the server name, the server SHOULD take one of two
> actions: abort the handshake by sending a fatal
> unrecognized_name(112) alert, or continue the handshake using a
> default credential. Sending a warning-level alert such as
> unrecognized_name(112), but continuing the handshake, is NOT
> RECOMMENDED because the client's expected behavior in response to
> this is unpredictable.

The last sentence makes it unclear whether sending the alert is not
recommended or if continuing the handshake is not recommended.

Mike

v2.23.0 | Report a Bug | By Email