IETF Logo Mail Archive

Re: [certid] Comments on draft-saintandre-tls-server-id-check-03

ArkanoiD <ark@eltex.net> Wed, 12 May 2010 23:02 UTC

Return-Path: <ark@eltex.net>
X-Original-To: certid@core3.amsl.com
Delivered-To: certid@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE7303A69BF for <certid@core3.amsl.com>; Wed, 12 May 2010 16:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.105
X-Spam-Level: *
X-Spam-Status: No, score=1.105 tagged_above=-999 required=5 tests=[AWL=-1.600, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_17=0.6, RDNS_NONE=0.1]
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 DorEVJyPiOdd for <certid@core3.amsl.com>; Wed, 12 May 2010 16:02:59 -0700 (PDT)
Received: from lebedev-225.itcwin.com (unknown [88.201.200.225]) by core3.amsl.com (Postfix) with ESMTP id E22CA3A6767 for <certid@ietf.org>; Wed, 12 May 2010 16:02:58 -0700 (PDT)
Received: from lebedev-225.itcwin.com (ark@localhost.my.domain [127.0.0.1]) by lebedev-225.itcwin.com (8.14.3/8.14.3) with ESMTP id o4CN2c02009419; Thu, 13 May 2010 03:02:38 +0400 (MSD)
Received: (from ark@localhost) by lebedev-225.itcwin.com (8.14.3/8.14.3/Submit) id o4CN2cGx029902; Thu, 13 May 2010 03:02:38 +0400 (MSD)
X-Authentication-Warning: lebedev-225.itcwin.com: ark set sender to ark@eltex.net using -f
Date: Thu, 13 May 2010 03:02:38 +0400
From: ArkanoiD <ark@eltex.net>
To: Love H?rnquist ?strand <lha@apple.com>
Message-ID: <20100512230238.GA22246@eltex.net>
References: <4BEB0FBF.5070502@KingsMountain.com> <4BEB2DC7.5020409@stpeter.im> <B6E22FEA-57C7-46D9-B820-DA51936C6E71@apple.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
In-Reply-To: <B6E22FEA-57C7-46D9-B820-DA51936C6E71@apple.com>
User-Agent: Mutt/1.4.2.3i
Cc: certid@ietf.org
Subject: Re: [certid] Comments on draft-saintandre-tls-server-id-check-03
X-BeenThere: certid@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Representation and verification of identity in certificates <certid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/certid>, <mailto:certid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/certid>
List-Post: <mailto:certid@ietf.org>
List-Help: <mailto:certid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/certid>, <mailto:certid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 May 2010 23:03:00 -0000

It does not really answer the question, we should analyse certificates seen
"in the wild" ;-)

On Wed, May 12, 2010 at 03:58:23PM -0700, Love H?rnquist ?strand wrote:
> 
> 12 maj 2010 kl. 15:37 skrev Peter Saint-Andre:
> 
> >> So I'm not sure right now what to say about that. I suspect we can still
> >> stipulate that the only RDN having attr type of CN that we'll pay
> >> attention to is the one at the far end of the RDN sequence comprising
> >> the DN.
> > 
> > We can stipulate that, but is it realistic?
> 
> Yes, since that's what RFC 2818 said.

v2.8.7 | Report a Bug | By Email