tree d99e9bb98f7bd7edb64a78baef2176d42cde62a8
parent 2e52121acd2befd3ad04953f94fae5e80d84b1a2
author Adam Langley <agl@chromium.org> 1405532757 -0700
committer Adam Langley <agl@google.com> 1405537178 +0000

Don't delay CKX and Finished for False Start.

Android never did this - they patched out the point in the code that set
the SSL3_FLAGS_DELAY_CLIENT_FINISHED flag when doing False Start.
Also, from the unittests it appears that NSS doesn't do this either.
Thus this change brings BoringSSL into line with existing behaviour.

SSL3_FLAGS_DELAY_CLIENT_FINISHED wasn't introduced with False Start,
it's an option in vanilla OpenSSL. But I can't find anything that uses
it and, since it's going to be untested, I've removed it completely in
this change.

Change-Id: I910537bfa35e74ab88778b83612cf5607d485969
Reviewed-on: https://boringssl-review.googlesource.com/1221
Reviewed-by: David Benjamin <davidben@chromium.org>
Reviewed-by: Adam Langley <agl@google.com>