Re: [plasma] KEK usage

Trevor Freeman <> Fri, 28 October 2011 17:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4877121F8514 for <>; Fri, 28 Oct 2011 10:39:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -110.766
X-Spam-Status: No, score=-110.766 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id pdSFyryN1yA6 for <>; Fri, 28 Oct 2011 10:39:42 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 96B1021F84FA for <>; Fri, 28 Oct 2011 10:39:42 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Fri, 28 Oct 2011 10:39:42 -0700
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Fri, 28 Oct 2011 10:39:42 -0700
Received: from ([fe80::cc46:3da5:bed6:8dfc]) by ([fe80::d940:e316:1daa:5e6a%10]) with mapi id 14.02.0247.002; Fri, 28 Oct 2011 10:39:41 -0700
From: Trevor Freeman <>
To: "Fitch, Scott C" <>, "" <>
Thread-Topic: KEK usage
Thread-Index: AcyTRgPodLuEJ3NEQcqy3+T3/w0AYACUW+7A
Date: Fri, 28 Oct 2011 17:39:41 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-GB, en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [plasma] KEK usage
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The PoLicy Augmented S/Mime \(plasma\) bof discussion list." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 28 Oct 2011 17:39:44 -0000

If the policy does not want to disclose the KEK to the PDP in the clear, then they have to do early key binding like S/MIME does today. You discover the user's encryption key and encrypt the KEK using their public key to create a recipient info structure which you include for the PDP. The PDP would need to request a claim about the identity of the recipient's public key and then it can release the appropriate recipient info structure. 

-----Original Message-----
From: [] On Behalf Of Fitch, Scott C
Sent: Tuesday, October 25, 2011 11:48 AM
Subject: [plasma] KEK usage

I have a question on using a KEK as described in Section 4.2. It states:

The [Content Creation] PEP submits the CEK, the set of requires policies to be applied and the hash of the encrypted content to the PDP. The CEK can be a raw key or a CEK key encrypted by a KEK if the user does not want the PDP to have the ability to access the plain text data.

In the case of encrypting the CEK with a KEK, whose key is used in that case? And how will the recipient decrypt it? I didn't see the corresponding steps listed in the Content Consuming sequence.

plasma mailing list