[smime] Use of subjectKeyIdentifier

Michael Ströder <michael@stroeder.com> Wed, 31 March 2010 17:26 UTC

Return-Path: <michael@stroeder.com>
X-Original-To: smime@core3.amsl.com
Delivered-To: smime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 480D93A6B7C for <smime@core3.amsl.com>; Wed, 31 Mar 2010 10:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.016
X-Spam-Level:
X-Spam-Status: No, score=-2.016 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HELO_MISMATCH_COM=0.553, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 vbdpS5gq-Ogt for <smime@core3.amsl.com>; Wed, 31 Mar 2010 10:26:14 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id BD1513A6A59 for <smime@ietf.org>; Wed, 31 Mar 2010 10:19:12 -0700 (PDT)
Received: from srv1.stroeder.com (srv1.stroeder.com [213.240.180.113]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id o2VHJf7k000267 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-smime@imc.org>; Wed, 31 Mar 2010 10:19:43 -0700 (MST) (envelope-from michael@stroeder.com)
Received: from localhost (localhost [127.0.0.1]) by srv1.stroeder.com (Postfix) with ESMTP id 8F8AA4E10B for <ietf-smime@imc.org>; Wed, 31 Mar 2010 19:19:39 +0200 (CEST)
X-Virus-Scanned: amavisd-new at stroeder.com
Received: from srv1.stroeder.com ([127.0.0.1]) by localhost (srv1.stroeder.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e9hFI4Bk1urO for <ietf-smime@imc.org>; Wed, 31 Mar 2010 19:19:38 +0200 (CEST)
Received: from [10.1.0.2] (unknown [10.1.0.2]) by srv1.stroeder.com (Postfix) with ESMTP id 9ACD64E102 for <ietf-smime@imc.org>; Wed, 31 Mar 2010 19:19:36 +0200 (CEST)
Message-ID: <4BB38427.40502@stroeder.com>
Date: Wed, 31 Mar 2010 19:19:35 +0200
From: =?ISO-8859-1?Q?Michael_Str=F6der?= <michael@stroeder.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 SeaMonkey/2.0.4
MIME-Version: 1.0
To: ietf-smime@imc.org
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [smime] Use of subjectKeyIdentifier
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Mar 2010 17:26:15 -0000

HI!

If an S/MIME cert does not contain a subjectKeyIdentifier extension is a
sending S/MIME MUA allowed to generate RecipientInfos referencing the
receiver's cert by (self-calculated) subjectKeyIdentifier (instead of issuer
name and serial number)?

IMHO RFC 5750 is not really clear on that.

Ciao, Michael.