tree f6e9e685b20d990828c6ff0c70ca5ffb92c7bfb8
parent 5902657734e2a796a514731e0fd0e80081ae43dc
author David Benjamin <davidben@google.com> 1585002549 -0400
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 1586458229 +0000

Add SSL_SESSION_copy_without_early_data.

While we could store an extra boolean along with each session in the
session cache and then disable early data on a per-socket level, that
causes SSL_early_data_reason to report confusing values. Clearing it
at the session seems simpler. Since sessions are intended to be
mutable, do this as a copy operation.

Bug: chromium:1066623
Change-Id: I599b1559b696805e330ab5c2d61e4158440daef8
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/40464
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Steven Valdez <svaldez@google.com>
Reviewed-by: David Benjamin <davidben@google.com>