Re: [plasma] Who creates the 'keyIdentifier'?

"Jim Schaad" <jimsch@nwlink.com> Wed, 18 July 2012 22:22 UTC

Return-Path: <jimsch@nwlink.com>
X-Original-To: plasma@ietfa.amsl.com
Delivered-To: plasma@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1116611E81C0 for <plasma@ietfa.amsl.com>; Wed, 18 Jul 2012 15:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LXEEphFYUA2X for <plasma@ietfa.amsl.com>; Wed, 18 Jul 2012 15:22:34 -0700 (PDT)
Received: from smtp4.pacifier.net (smtp4.pacifier.net [64.255.237.176]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC4211E80BC for <plasma@ietf.org>; Wed, 18 Jul 2012 15:22:34 -0700 (PDT)
Received: from Tobias (mail.augustcellars.com [50.34.17.238]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jimsch@nwlink.com) by smtp4.pacifier.net (Postfix) with ESMTPSA id 2A54238F06; Wed, 18 Jul 2012 15:23:25 -0700 (PDT)
From: "Jim Schaad" <jimsch@nwlink.com>
To: "'Alan Borland'" <alan.b.borland@googlemail.com>, <plasma@ietf.org>
References: <CALtitoaWM2AwJR3JWFjUiAmc7yKMU4O2sV6tm=s65ibLi7r2iA@mail.gmail.com>
In-Reply-To: <CALtitoaWM2AwJR3JWFjUiAmc7yKMU4O2sV6tm=s65ibLi7r2iA@mail.gmail.com>
Date: Wed, 18 Jul 2012 15:21:59 -0700
Message-ID: <02d101cd6533$c0239fb0$406adf10$@nwlink.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_02D2_01CD64F9.13C711A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGBSHVfCS46jvYtcH0EF1jjoC1EJJfH1m9g
Content-Language: en-us
Subject: Re: [plasma] Who creates the 'keyIdentifier'?
X-BeenThere: plasma@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The PoLicy Augmented S/Mime \(plasma\) bof discussion list." <plasma.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/plasma>, <mailto:plasma-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/plasma>
List-Post: <mailto:plasma@ietf.org>
List-Help: <mailto:plasma-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/plasma>, <mailto:plasma-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jul 2012 22:22:36 -0000

The value is created by the client and passed to the server.  If there is no
field this is an oversight on my part.  I will look at this later today.

 

From: plasma-bounces@ietf.org [mailto:plasma-bounces@ietf.org] On Behalf Of
Alan Borland
Sent: Wednesday, July 18, 2012 1:32 AM
To: plasma@ietf.org
Subject: [plasma] Who creates the 'keyIdentifier'?

 

I'm trying to understand who generates the 'KeyIdentifier' element in the
'KEKIdentifier' structure of the 'RecipientInfo' created by the client.  

 

Is it the client?  The Plasma CMS Processing document, Page 8, describes how
the 'KeyIdentifier' is a random generated value (Created by the client?).  

 

Is it the Plasma Server?  On Page 13 the KekIdentifier is a value that
matches the KEKIdentifier.KeyIdentifier value in the recipient info
information (I have read this to mean that the EPS-LockBox version must
match the KeyIdentifier in the envelopedData created by the client, meaning
the KeyIdentifer must be transported between client and plasma server). 

 

>From this I thought the client created the random value and passed it across
to the server inside the 'GetCMSToken' request. However, I can't see this
described in the request.  Is this missing from the request documentation,
or does this Imply that the client has to extract the KeyIdentifer from the
EPS-KEK returned in the GetCMSToken response, but this is encrypted and only
the Plasma Server has access to this.  Or have I mis-read this completely?

 

Alan.

 

Boldon James.