Ensure read records are marked as read
authorMatt Caswell <matt@openssl.org>
Tue, 21 Jun 2016 14:25:53 +0000 (15:25 +0100)
committerMatt Caswell <matt@openssl.org>
Mon, 27 Jun 2016 13:51:03 +0000 (14:51 +0100)
commit63916e9a234c1e6bbf82cc21b7d2e39cdecb30d0
tree2f9259c6c602a1dc47df4433f72022dd51c37a3d
parent6f4a6a5cd472d56937a8e9d6665e7c9cc6b1b2e2
Ensure read records are marked as read

In some situations (such as when we receive a fragment of an alert)
we try to get the next packet but did not mark the current one as read,
meaning that we got the same record back again - leading to an infinite
loop.

Found using the BoringSSL test suite.

Reviewed-by: Andy Polyakov <appro@openssl.org>
ssl/record/rec_layer_s3.c