Re: [TLS] TLS and hardware security modules - some issues related to PKCS11

Pascal Urien <pascal.urien@gmail.com> Tue, 17 September 2013 12:57 UTC

Return-Path: <pascal.urien@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B853111E8242 for <tls@ietfa.amsl.com>; Tue, 17 Sep 2013 05:57:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 9MiCrIJq2EX7 for <tls@ietfa.amsl.com>; Tue, 17 Sep 2013 05:57:46 -0700 (PDT)
Received: from mail-bk0-x232.google.com (mail-bk0-x232.google.com [IPv6:2a00:1450:4008:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id F111B11E8441 for <tls@ietf.org>; Tue, 17 Sep 2013 05:57:09 -0700 (PDT)
Received: by mail-bk0-f50.google.com with SMTP id mz11so2104942bkb.23 for <tls@ietf.org>; Tue, 17 Sep 2013 05:57:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tvOUry6XVisiHWXBv2bM8w3LJXIbZ82mHhPN5GcgLI4=; b=xy71haz3o5gPONtkcCdMgxmAkbUskw41bqpNU7f42HzPs8AtXkAYtvhfzWyM02MJW8 HqFHJyOs77aNghVXaX44pMD0sb9UyM3SNiFFvOMD979dm0kWl+QCzmWxrfZPXHolO8as oO/4cHzVTSUwurP4BzJ8FMcBlWmSGTrw3CgHDpYjYZxB7PpIiLuMJi5OMPtE9c2j1jHa 3Y8wFOnlKdhEPsfqoy9Hzxj0cSFaaL3GvaSRbQ1+spU0zID5f4R9jPjXlU3F8sispVo+ s0cc/vxa+e73lNIeQYCCHjCOKealAng0hNCjq5C7XXLPWsYlzzt5c+bQmoXnDU8Zp+dt Ar3g==
MIME-Version: 1.0
X-Received: by 10.205.105.73 with SMTP id dp9mr1517627bkc.33.1379422620627; Tue, 17 Sep 2013 05:57:00 -0700 (PDT)
Received: by 10.204.171.207 with HTTP; Tue, 17 Sep 2013 05:57:00 -0700 (PDT)
In-Reply-To: <20130917124948.8DEFB1A974@ld9781.wdf.sap.corp>
References: <52379643.7070705@nthpermutation.com> <20130917124948.8DEFB1A974@ld9781.wdf.sap.corp>
Date: Tue, 17 Sep 2013 14:57:00 +0200
Message-ID: <CAEQGKXQ8cwSxkmM5H0Gooi4dFFr0q9TNT1HpBjkTrTSMUdDWSQ@mail.gmail.com>
From: Pascal Urien <pascal.urien@gmail.com>
To: mrex@sap.com
Content-Type: multipart/alternative; boundary=f46d042186ad4c6f1204e693db73
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] TLS and hardware security modules - some issues related to PKCS11
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.12
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/options/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: Tue, 17 Sep 2013 12:57:51 -0000

Why don't you realize a TLS stack in a secure element ?. For both full and
resume mode , in order to protect the master secret

see
http://www.ethertrust.com/wp-content/themes/ethertrust/about_ethertrust.pdf

Pascal


2013/9/17 Martin Rex <mrex@sap.com>

> I fail to understand what you're trying to protect.
>
> The master secret of a session is never a secret that is hidding
> within the hardware module, instead, it is something known to the
> calling TLS protocol stack and part of the TLS session cache.
>
> For vanilla RSA cipher suites, it is deterministically derived
> from randomness generated by the client and conveyed under
> RSA encryption, deterministically combined with data known
> in plain to the TLS protocol stack.
>
> -Martin
> _______________________________________________
> TLS mailing list
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
>