Re: [TLS] Proposed text for removing renegotiation

Hubert Kario <hkario@redhat.com> Fri, 30 May 2014 09:36 UTC

Return-Path: <hkario@redhat.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4042F1A078F for <tls@ietfa.amsl.com>; Fri, 30 May 2014 02:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level:
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tZQAzDtk_cEy for <tls@ietfa.amsl.com>; Fri, 30 May 2014 02:36:10 -0700 (PDT)
Received: from mx6-phx2.redhat.com (mx6-phx2.redhat.com [209.132.183.39]) by ietfa.amsl.com (Postfix) with ESMTP id 650ED1A03D3 for <tls@ietf.org>; Fri, 30 May 2014 02:36:10 -0700 (PDT)
Received: from zmail11.collab.prod.int.phx2.redhat.com (zmail11.collab.prod.int.phx2.redhat.com [10.5.83.13]) by mx6-phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s4U9a3Wh019344; Fri, 30 May 2014 05:36:03 -0400
Date: Fri, 30 May 2014 05:36:03 -0400
From: Hubert Kario <hkario@redhat.com>
To: James Cloos <cloos@jhcloos.com>
Message-ID: <447419780.17071094.1401442563129.JavaMail.zimbra@redhat.com>
In-Reply-To: <m3mwe0i8as.fsf@carbon.jhcloos.org>
References: <CABkgnnXaLKmxXL01hQEdxHSNGt3nZQQNBLDD5H2LqBzTo3vK4g@mail.gmail.com> <CABkgnnW0YAhsbMoN0JSdWWpxt9TsOWpvq3c67cw8_eyt4mprbA@mail.gmail.com> <m2vbspv8w1.fsf@localhost.localdomain> <CABkgnnWfM8eDALtGmpHBeHScy21fzTqv8+C0ajnDhAO=OBziZg@mail.gmail.com> <1414735395.16311772.1401366314379.JavaMail.zimbra@redhat.com> <CABkgnnWqqEnayrgAwVA-x_O5rkvWjtcH+g=TpE1Ztmk_JvuNYg@mail.gmail.com> <739427058.16557109.1401382793847.JavaMail.zimbra@redhat.com> <m3mwe0i8as.fsf@carbon.jhcloos.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Originating-IP: [10.5.82.12]
X-Mailer: Zimbra 8.0.6_GA_5922 (ZimbraWebClient - FF29 (Linux)/8.0.6_GA_5922)
Thread-Topic: Proposed text for removing renegotiation
Thread-Index: U8N83OiZXy6RelEbcThfWtdpJCttUg==
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/lP4JamIAr3BVMovzeBzAWSUKyUA
Cc: Geoffrey Keating <geoffk@geoffk.org>, tls@ietf.org
Subject: Re: [TLS] Proposed text for removing renegotiation
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 30 May 2014 09:36:14 -0000

----- Original Message -----
> From: "James Cloos" <cloos@jhcloos.com>
> To: "Hubert Kario" <hkario@redhat.com>
> Cc: "Martin Thomson" <martin.thomson@gmail.com>, "Geoffrey Keating" <geoffk@geoffk.org>, tls@ietf.org
> Sent: Thursday, May 29, 2014 11:28:02 PM
> Subject: Re: [TLS] Proposed text for removing renegotiation
> 
> >>>>> "HK" == Hubert Kario <hkario@redhat.com> writes:
> 
> >>> Transferring 64GB of data with TLS over loopback on a relatively modern
> >>> machine (even without AES-NI) takes less than an hour. I wouldn't
> >>> call it going to great lengths to test.
> 
> Did you mean something other that GB there?
> 
> 150Mbit/s is a bit slow for loopback. ☺

It's not slow for AES though.

That was the example of slowest performance for this, in a full functional test -
where the application is in production configuration. That is, it does everything
from certificate verification to AES-GCM crypto, all in software on a few year
old hardware with encryption and decryption running in parallel.

With AES-GCM done in hardware (e.g. AES-NI) on a multi core CPU, the test shouldn't
take more than 10-15 minutes.
-- 
Regards,
Hubert Kario