otp.git - Mirror of Erlang/OTP repository.

Age	Commit message (Collapse)	Author
2018-11-30	Handle dead sender at terminate	Raimo Niskanen

2018-11-23	Improve dist send throughput	Raimo Niskanen

2018-11-07	ssl: Correct gen_statem return value	Ingela Anderton Andin
	Could cause renegotiation to fail
2018-10-11	ssl: Fix up incorrect automatic merge	Ingela Anderton Andin

2018-10-11	Merge branch 'ingela/maint/ssl/packet-options-to-tls-sender/OTP-15348' into ↵	Ingela Anderton Andin
	maint Conflicts: lib/ssl/src/tls_sender.erl
2018-10-11	ssl: TLS sender process needs to get updates of the socket option packet	Ingela Anderton Andin
	If the socket option is set to {packet, 1\|2\|3\|4} sender process needs to add a packet length header. If packet is changed with ssl:setopts/2 this needs to be communicated to tls_sender.
2018-10-10	ssl: ERL-738 - Correct alert handling with new TLS sender process	Ingela Anderton Andin
	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.
2018-10-10	ssl: TLS sender process needs to get updates of the socket option packet	Ingela Anderton Andin
	If the socket option is set to {packet, 1\|2\|3\|4} sender process needs to add a packet length header. If packet is changed with ssl:setopts/2 this needs to be communicated to tls_sender.
2018-10-08	ssl: ERL-738 - Correct alert handling with new TLS sender process	Ingela Anderton Andin
	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.
2018-09-20	ssl: Move link to correct process	Ingela Anderton Andin
	The link should be between the connection process and the tls_sender process. But the start of the tls_sender process needs to be done by the process that also starts the connection process in order to correctly create the opaque #ssl_socket{}.
2018-08-27	ssl: Improve close handling	Ingela Anderton Andin
	We want to make sure that the sender process that may get stuck in prim_inet:send will die if the tls_connection process is terminated. And we also like to make sure that it terminates as gracefully as possible. So when the tls_connection process dies it spawns a killer process that will brutaly kill the sender if it is unresponsive and does not terminate due to its monitor of the tls_connetion process triggering. When the sender process also acts as distribution controller it may also have other processess that it is linked with that it should bring down or that could bring the connection down.
2018-08-27	ssl: Adopt distribution over TLS to use new sender process	Ingela Anderton Andin

2018-08-27	ssl: Add new sender process for TLS state machine	Ingela Anderton Andin
	Separate sending and receiving when using TCP as transport as prim_inet:send may block which in turn may result in a deadlock between two Erlang processes communicating over TLS, this is especially likely to happen when running Erlang distribution over TLS.