aboutsummaryrefslogtreecommitdiffstats
path: root/lib/ssl/src/ssl.app.src
diff options
context:
space:
mode:
authorIngela Anderton Andin <[email protected]>2018-10-04 08:14:37 +0200
committerIngela Anderton Andin <[email protected]>2018-10-10 10:28:59 +0200
commita210b0ed49f026919eea9fcef50f140a037b0982 (patch)
tree7b7c4adffba04152437d5906aed46a5153448e76 /lib/ssl/src/ssl.app.src
parent377f19f25aeec6939a6728bd0c4910086c22ccdc (diff)
downloadotp-a210b0ed49f026919eea9fcef50f140a037b0982.tar.gz
otp-a210b0ed49f026919eea9fcef50f140a037b0982.tar.bz2
otp-a210b0ed49f026919eea9fcef50f140a037b0982.zip
ssl: ERL-738 - Correct alert handling with new TLS sender process
With the new TLS sender process, solving ERL-622, TLS ALERTs sent in the connection state must be encrypted and sent by the TLS sender process. This to make sure that the correct encryption state is used to encode the ALERTS. Care must also be taken to ensure a graceful close down behavior both for normal shutdown and downgrading from TLS to TCP. The original TR ERL-738 is verified by cowboy tests, and close down behavior by our tests. However we alas have not been able to yet create a minimal test case for the originating problem. Also it seems it has become less likely that we run in to the TCP delivery problem, that is the guarantee is only on transport level, not application level. Keep work around function in ssl_test_lib but we can have better test as long as we do not get to much wobbling tests.
Diffstat (limited to 'lib/ssl/src/ssl.app.src')
0 files changed, 0 insertions, 0 deletions