Re: [TLS] Hardware Implementations .. Re: On Curve25519 and other possibilities (e.g. ietf256p, ietf384p, ietf521p,

Joachim Strömbergson <joachim@secworks.se> Fri, 27 June 2014 08:21 UTC

Return-Path: <joachim@secworks.se>
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 8BB461B2CDA for <tls@ietfa.amsl.com>; Fri, 27 Jun 2014 01:21:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.25
X-Spam-Level:
X-Spam-Status: No, score=-1.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3] autolearn=no
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 HIHyKHmjAjyO for <tls@ietfa.amsl.com>; Fri, 27 Jun 2014 01:21:03 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6EA41B2CCA for <tls@ietf.org>; Fri, 27 Jun 2014 01:21:02 -0700 (PDT)
Received: from secworks82.gotanet.se (unknown [62.80.223.82]) by mail.frobbit.se (Postfix) with ESMTPSA id EAA801FD5F; Fri, 27 Jun 2014 10:21:00 +0200 (CEST)
Message-ID: <53AD296C.40204@secworks.se>
Date: Fri, 27 Jun 2014 10:21:00 +0200
From: =?ISO-8859-1?Q?Joachim_Str=F6mbergson?= <joachim@secworks.se>
User-Agent: Postbox 3.0.9 (Macintosh/20140129)
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
References: <53AC97B8.2080909@nthpermutation.com> <53AD134E.9010903@akr.io> <53AD27B4.2060901@gmx.net>
In-Reply-To: <53AD27B4.2060901@gmx.net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/tHcOr48oamnDuVRLfuTnkzrh_60
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Hardware Implementations .. Re: On Curve25519 and other possibilities (e.g. ietf256p, ietf384p, ietf521p,
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: joachim@secworks.se
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, 27 Jun 2014 08:21:04 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Aloha!

Hannes Tschofenig wrote:
> Based on the discussions at the IRTF interim meeting a little while
> ago I took the Curve25519 code and ported it to mbed (the online
> development platform ARM provides, see https://mbed.org).
> 
> I wanted to know how long it takes to generate key pairs since this
> is one of the most performance-demanding operations. To my surprise
> it was rather fast:
> 
> - 0.278821 seconds for generating a Curve25519 key pair on a Cortex
> M0 (FRDM-KL25Z, 48MHz) https://mbed.org/handbook/mbed-FRDM-KL25Z
> 
> - 0.047394 seconds for generating a Curve25519 key pair on a Cortex
> M3 (LPC1768, 96MHz) https://mbed.org/platforms/mbed-LPC1768/

Great work and information! Have you done a write-up of the results? I'm
very interested in info on the code size and data memory during operation.

> (Note that I did not include the calculation of the random numbers
> in those numbers since it will depend on a variety of factors,
> including the hardware capabilities of the used board.)

So how did you do the random generation? Fixed values or some other
mechanism?

- -- 
Med vänlig hälsning, Yours

Joachim Strömbergson - Alltid i harmonisk svängning.
========================================================================
 Joachim Strömbergson          Secworks AB          joachim@secworks.se
========================================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJTrSlrAAoJEF3cfFQkIuyNOy4P/35il82TWxRBZwC3XrFGoRIw
M7FqFmnmgXibjU1GxDXvYAuwTXEyY27vNooPZVBzXVtp1Y834MGQjPwCEec2aYaL
/LanQrxoOiwOFLBSYahn867FiM2Trc/w0gyVJ+tOI9tmp6FHbzWzTUHnCbCGnOeS
PDh1Zy39/QEHElXc8FAJGJTf7c+W/bv3YbTBJC3E0r/g2NR94Okg0AWKYFQbDerO
Ac+DMIYIBy3mlz0vzrIOs2f43fcWHitZKGhZ/5iygY9Qzg1LG59oygr0lSTvIp5H
GmhUVYmi8Rhw0VzcQbxaJnivWmatR2kC6aRka4n0Ifxr7dkj70mIm9yOiCxrBJse
fnfhXPO97KkyIV3dCRT9aVTBcDIqeMahQ5Dp+WLLNmE8d4SXgQU0h553Xutygnft
GtB4SaE+CIJNN3Df+d9I1JFTWZicKizs+UeRl2u8J0B8LH0oqgNwTnLAswkyhyZH
nWYXBZjp3lFE+IuoolqcpYVwWlO17ocVLmw1a0+M3k9zq1g8gAGa+yPMY6CvGcyP
58RDVHx+sfWH0O+DWsX90odiqy7cIfLSfk2ECA9xHTFmoQ0N9oWS/Nh0rfnZ3Ukq
KxwQgFXNBcV45229Cl1LeavDkqc0m/oL0ilLxMT8L78spPoTfbz9J9GBMV4JNRDn
cuf6ieDceHSnQ+1h5OD5
=QKHI
-----END PGP SIGNATURE-----