tree 95b5b5c4edfbc0e61ed78ed30386f6a637e23057
parent c92f29dcc5e1e4f74fdcbcff0ca26db84b606b63
author David Benjamin <davidben@google.com> 1487357510 -0500
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 1487360999 +0000

Stop reporting SSL_R_SHUTDOWN_WHILE_IN_INIT.

This effectively reverts b9824e241746d70d985d1004078b5bad0ad9a75b. This
error seems to have mostly just caused confusion in logs and the
occasional bug around failing to ERR_clear_error. Consumers tend to
blindly call SSL_shutdown when tearing down an SSL (to avoid
invalidating sessions). This means handshake failures trigger two
errors, which is screwy.

Go back to the old behavior where SSL_shutdown while SSL_in_init
silently succeeds.

Change-Id: I1fcfc92d481b97c840847dc39afe59679cd995f2
Reviewed-on: https://boringssl-review.googlesource.com/13909
Commit-Queue: David Benjamin <davidben@google.com>
Commit-Queue: Steven Valdez <svaldez@google.com>
Reviewed-by: Steven Valdez <svaldez@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>