tree cf561bbccd8392dd76bdb7e26fd3993d51172c62
parent 4119d42e7c240ad7a651b0871e1f5ac9bbae7e68
author David Benjamin <davidben@chromium.org> 1451076014 -0500
committer Adam Langley <alangley@gmail.com> 1452890805 +0000

Fill in ssl->session->cipher when resumption is resolved.

Doing it at ChangeCipherSpec makes it be set twice and, more
importantly, causes us to touch SSL_SESSION objects on resumption. (With
a no-op change, but this still isn't a good idea.)

This should actually let us get rid of ssl->s3->tmp.new_cipher but some
of external code accesses that field directly.

Change-Id: Ia6b7e0964c1b430f963ad0b1a5417b339b7b19d3
Reviewed-on: https://boringssl-review.googlesource.com/6833
Reviewed-by: Adam Langley <alangley@gmail.com>