25fe85b38c
If cert_cb runs asynchronously, we end up repeating a large part of very stateful ClientHello processing. This seems to be mostly fine and there are few users of server-side cert_cb (it's a new API in 1.0.2), but it's a little scary. This is also visible to external consumers because some callbacks get called multiple times. We especially should try to avoid that as there is no guarantee that these callbacks are idempotent and give the same answer each time. Change-Id: I212b2325eae2cfca0fb423dace101e466c5e5d4e Reviewed-on: https://boringssl-review.googlesource.com/10224 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> |
||
---|---|---|
.. | ||
openssl |