New issue
Advanced search Search tips

Issue 801302 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug

Blocked on:
issue 809779



Sign in to add a comment

Run latency experiments to evaluate different families of post-quantum key agreements.

Project Member Reported by agl@chromium.org, Jan 11 2018

Issue description

In order to effectively evaluate the tradeoffs between different families of potential post-quantum key exchange algorithms, we need better data on the latency impact of the larger TLS messages.

We previously measured NewHope[1], but that didn't cover mobile.

In the first phase of this experiment we aim to measure the latency of additional ClientHello bytes for three sizes which approximate supersingular isogenies, structured lattices, and unstructured lattices.

[1] https://security.googleblog.com/2016/07/experimenting-with-post-quantum.html
 
Project Member

Comment 1 by bugdroid1@chromium.org, Jan 17 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/074164133fddd6c98ef26cb157996ca553261427

commit 074164133fddd6c98ef26cb157996ca553261427
Author: Adam Langley <agl@chromium.org>
Date: Wed Jan 17 03:27:32 2018

Enable Finch-controllable dummy post-quantum padding.

This change allows Finch control of the dummy post-quantum padding
extension which will be used to measure the additional latency expected
from sending post-quantum public keys from various families in a future
PQ TLS 1.3 configuration.

Bug: 801302
Change-Id: Ie8471c49f71b71cb9f3d1b45d1f4ff66c57ab438
Reviewed-on: https://chromium-review.googlesource.com/862393
Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#529573}
[modify] https://crrev.com/074164133fddd6c98ef26cb157996ca553261427/net/socket/ssl_client_socket_impl.cc

Comment 2 by agl@chromium.org, Jan 31 2018

Labels: -Type-Task OS-Android OS-Chrome OS-Linux OS-Mac OS-Windows Type-Launch

Comment 3 by agl@chromium.org, Feb 6 2018

Blockedon: 809779
Labels: -Type-Launch Type-Bug
Project Member

Comment 4 by bugdroid1@chromium.org, Mar 8 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/95fa02ecb82a8785c220d6404b1cb7c46eb8d494

commit 95fa02ecb82a8785c220d6404b1cb7c46eb8d494
Author: Adam Langley <agl@chromium.org>
Date: Thu Mar 08 20:06:33 2018

Record TLS latency in a special histogram when dummy PQ padding was used.

The second phase of the post-quantum latency experiment involves sending
and receiving dummy data. We will deploy some number of public servers
that will echo the padding extension and this change adds latency
measurements for those cases.

Since the latency of servers that support echoing the extension will be
different from the latency of all TLS servers, we cannot use the
existing, general latency histogram for this and our control group will
send a 1-byte extension rather than no extension at all.

Bug: 801302
Change-Id: I017324047f66f0889df247b6581670f44e9e5fb5
Reviewed-on: https://chromium-review.googlesource.com/954329
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541876}
[modify] https://crrev.com/95fa02ecb82a8785c220d6404b1cb7c46eb8d494/net/socket/ssl_client_socket_impl.cc
[modify] https://crrev.com/95fa02ecb82a8785c220d6404b1cb7c46eb8d494/net/socket/ssl_client_socket_pool.cc
[modify] https://crrev.com/95fa02ecb82a8785c220d6404b1cb7c46eb8d494/net/ssl/ssl_info.cc
[modify] https://crrev.com/95fa02ecb82a8785c220d6404b1cb7c46eb8d494/net/ssl/ssl_info.h
[modify] https://crrev.com/95fa02ecb82a8785c220d6404b1cb7c46eb8d494/tools/metrics/histograms/histograms.xml

Sign in to add a comment