diff options
| author | Adam Langley <agl@chromium.org> | 2014-07-16 21:45:57 +0400 |
|---|---|---|
| committer | Adam Langley <agl@google.com> | 2014-07-16 22:59:38 +0400 |
| commit | 045cc5590a214a0efb982d028a4f1f0e9dfe3314 (patch) | |
| tree | d99e9bb98f7bd7edb64a78baef2176d42cde62a8 /ssl/d1_clnt.c | |
| parent | 2e52121acd2befd3ad04953f94fae5e80d84b1a2 (diff) | |
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>
Diffstat (limited to 'ssl/d1_clnt.c')
| -rw-r--r-- | ssl/d1_clnt.c | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/ssl/d1_clnt.c b/ssl/d1_clnt.c index 538aa60a..63d31f2f 100644 --- a/ssl/d1_clnt.c +++ b/ssl/d1_clnt.c @@ -454,12 +454,6 @@ int dtls1_connect(SSL *s) if (s->hit) { s->s3->tmp.next_state=SSL_ST_OK; - if (s->s3->flags & SSL3_FLAGS_DELAY_CLIENT_FINISHED) - { - s->state=SSL_ST_OK; - s->s3->flags|=SSL3_FLAGS_POP_BUFFER; - s->s3->delay_buf_pop_ret=0; - } } else { |