diff options
| author | Ingela Anderton Andin <[email protected]> | 2018-10-04 08:14:37 +0200 |
|---|---|---|
| committer | Ingela Anderton Andin <[email protected]> | 2018-10-08 14:31:44 +0200 |
| commit | 7aefc2781e4be9f223dccfeb7f6eb502713fab0c (patch) | |
| tree | ec58aabae0723ecc230191d5fc4caca36658edee /lib/ssl/test/ssl_packet_SUITE.erl | |
| parent | 0cb5456831a99e21f11e7331b4e2c56849827944 (diff) | |
| download | otp-7aefc2781e4be9f223dccfeb7f6eb502713fab0c.tar.gz otp-7aefc2781e4be9f223dccfeb7f6eb502713fab0c.tar.bz2 otp-7aefc2781e4be9f223dccfeb7f6eb502713fab0c.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/test/ssl_packet_SUITE.erl')
0 files changed, 0 insertions, 0 deletions