tree 9892e88232e36681c68df283a98d1dc93f771a54
parent 8d4f7e5421a1a9fb9f51d62cd1dfa8edf429f2fe
author Adam Langley <agl@google.com> 1519853739 -0800
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 1519861133 +0000

Record whether dummy PQ padding was used.

On reflection, I think we'll need to note whether dummy PQ padding was
echoed on a given connection. Otherwise measurements in Chrome will be
mixed with cases where people have MITM proxies that ignored the
extension, or possibly Google frontends that haven't been updated.

Therefore this change will be used to filter latency measurements in
Chrome to only include those where the extension was echoed and we'll
measure at levels of 1 byte (for control), 400 bytes, and 1100 bytes.

This also makes it an error if the server didn't echo an extension of
the same length as was sent.

Change-Id: Ib2a0b29cfb8719a75a28f3cf96710c57d88eaa68
Reviewed-on: https://boringssl-review.googlesource.com/26284
Commit-Queue: Adam Langley <agl@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
Reviewed-by: David Benjamin <davidben@google.com>