IETF Logo Mail Archive

Re: [TLS] User Defined Key Pair

"Salz, Rich" <rsalz@akamai.com> Mon, 24 June 2013 16:33 UTC

Return-Path: <rsalz@akamai.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 9401E11E8162 for <tls@ietfa.amsl.com>; Mon, 24 Jun 2013 09:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.366
X-Spam-Level:
X-Spam-Status: No, score=-2.366 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, HTML_MESSAGE=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 8UlbKtTkFjQ7 for <tls@ietfa.amsl.com>; Mon, 24 Jun 2013 09:33:18 -0700 (PDT)
Received: from prod-mail-xrelay05.akamai.com (prod-mail-xrelay05.akamai.com [96.6.114.97]) by ietfa.amsl.com (Postfix) with ESMTP id 91C6621F9EB1 for <tls@ietf.org>; Mon, 24 Jun 2013 09:33:17 -0700 (PDT)
Received: from prod-mail-xrelay05.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id DC9381C47DF; Mon, 24 Jun 2013 16:33:14 +0000 (GMT)
Received: from prod-mail-relay03.akamai.com (prod-mail-relay03.akamai.com [172.27.8.26]) by prod-mail-xrelay05.akamai.com (Postfix) with ESMTP id CE1451C47DD; Mon, 24 Jun 2013 16:33:14 +0000 (GMT)
Received: from usma1ex-cashub.kendall.corp.akamai.com (usma1ex-cashub5.kendall.corp.akamai.com [172.27.105.21]) by prod-mail-relay03.akamai.com (Postfix) with ESMTP id B26AF2FD62; Mon, 24 Jun 2013 16:33:14 +0000 (GMT)
Received: from USMBX1.msg.corp.akamai.com ([169.254.1.138]) by USMA1EX-CASHUB5.kendall.corp.akamai.com ([172.27.105.21]) with mapi; Mon, 24 Jun 2013 12:33:10 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: "omh1835@rit.edu" <omh1835@rit.edu>
Date: Mon, 24 Jun 2013 12:33:09 -0400
Thread-Topic: [TLS] User Defined Key Pair
Thread-Index: Ac5w94RI99cNQASqTGGyT7nnr47KJwAAIOZQ
Message-ID: <2A0EFB9C05D0164E98F19BB0AF3708C711B251EF0E@USMBX1.msg.corp.akamai.com>
References: <CALxQUYGdagDHr+A4EKN5qPD1jZG+dH8PHwb0-fKJVUN_vC1MSg@mail.gmail.com> <2A0EFB9C05D0164E98F19BB0AF3708C711B251EE97@USMBX1.msg.corp.akamai.com> <CALxQUYGpcKPOAoZ8J56AoUGx8B3JhdmMche8MdQuqD_S=Y22ZQ@mail.gmail.com>
In-Reply-To: <CALxQUYGpcKPOAoZ8J56AoUGx8B3JhdmMche8MdQuqD_S=Y22ZQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_2A0EFB9C05D0164E98F19BB0AF3708C711B251EF0EUSMBX1msgcorp_"
MIME-Version: 1.0
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] User Defined Key Pair
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: Mon, 24 Jun 2013 16:33:23 -0000

Ø  On the browser level there should be a plugin that has a function to generate the key pair, that function must generate the same key pair for the same input parameters.


That's interesting.  This is the first system I've heard of that predictably generating a keypair is not only a feature, but a requirement.

I'm sure that I am not the only person who is bothered by the security implications of this.

                /r$
--
Principal Security Engineer
Akamai Technology
Cambridge, MA

v2.23.0 | Report a Bug | By Email