summaryrefslogtreecommitdiff
path: root/src/lib/libssl/s3_clnt.c
diff options
context:
space:
mode:
authortedu <>2014-04-24 04:31:30 +0000
committertedu <>2014-04-24 04:31:30 +0000
commitf0a36b9f78febba27b10781ea27c65ab1f85e385 (patch)
tree5378359d8dd39e01cd2d55845cdfd643fea4389a /src/lib/libssl/s3_clnt.c
parent329f166fa52c590ad4f531997654c913f07020cf (diff)
downloadopenbsd-f0a36b9f78febba27b10781ea27c65ab1f85e385.tar.gz
openbsd-f0a36b9f78febba27b10781ea27c65ab1f85e385.tar.bz2
openbsd-f0a36b9f78febba27b10781ea27c65ab1f85e385.zip
on today's episode of things you didn't want to learn:
do_ssl3_write() is recursive. and not in the simple, obvious way, but in the sneaky called through ssl3_dispatch_alert way. (alert level: fuchsia) this then has a decent chance of releasing the buffer that we thought we were going to use. check for this happening, and if the buffer has gone missing, put another one back in place. the direct recursive call is safe because it won't call ssl3_write_pending which is the function that actually does do the writing and releasing. as reported by David Ramos to openssl-dev: http://marc.info/?l=openssl-dev&m=139809493725682&w=2 ok beck
Diffstat (limited to 'src/lib/libssl/s3_clnt.c')
0 files changed, 0 insertions, 0 deletions