| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Implement encode/decode of psk_key_exchange_modes.
|
|
* ingela/ssl/correct-test-groups:
ssl: Correct groups
|
|
|
|
* ingela/ssl/continue-restructure-tests:
ssl: Avoid race in test code
ssl: Remove duplicate suite
ssl: Continue moving test form basic_SUITE to more appropriate suites
ssl: Add ssl_socket_SUITE
|
|
|
|
The suite was renamed tls_1_3_versions_SUITE but
apparently not via git, so the old file remained.
|
|
|
|
|
|
* ingela/ssl/sane-openssl:
ssl: Old OpenSSL implementation does not ignore trailing client hello data
|
|
Rename some of the structures and callback functions
(socket -> esock).
OTP-15955
|
|
Renamed constants (defines): SOCKET_ -> ESOCK_
OTP-15955
|
|
The naming "convention" for "top" functions of the esock
nif module was: The API functions where called nif_<foo>
This function did basic checks and arg extraction and then
called the a function called n<foo>, which was the one doing
the actual work.
Unfortunately, och some platforms (AIX) these second names,
n<foo>, clashed with system functions.
So, in order to avoid this, the naming of second function
has been changed to esock_<foo>.
OTP-15955
|
|
Removed unnecessary spec's causing dialyzer warnings.
|
|
Do not test TLS 1.0 with these old versions as we do send hello extensions
for those implementations that will use them, and trailing unknown data
should be ignored by RFC complient implementations.
|
|
Invalid guard tests for function sendto. It handled the,
invalid, socket address 'null'. Presumably, this was
intended for connected UDP sockets. Though, for a
connected (UDP) socket, the send function shall be used.
|
|
OTP-15904
|
|
OTP-15904
|
|
|
|
If we are not allowe to change ('eopnotsupp') the socket
option 'dontroute' then we skip the test case.
OTP-15904
|
|
The (second) notify test case had a faulty "condition" test
(which skipped the case in all cases except when it was
supposed to be skipped :)
Also, the test start and stop of the manager during the
test case has been adjusted. We try to keep track of how
long time each start and stop takes. And also, if they takes
to long, we skip the case.
|
|
Make stopping the manager (the entire manager sup tree)
more easy. The function(s) for starting and stopping the
manager that exist in the snmpm module is (mostly) intended
for testing, making the stop function more "potent" is no
real problem (now any process not just the parent) can stop
the manager process tree.
|
|
We have seen one case when it takes unreasonably long time
to start the manager, which causes the test case (notify_started01)
to fail. We try to monitor the start, and if it takes to long
a time, we instead skip.
|
|
* ingela/ssl/continue-test-restructure:
ssl: Move alert test to own suite
ssl: Move der_input and rizzo tests
|
|
Also clean up code after previous test moves
|
|
Also refactor Rizzo tests to minimize them to only test
what actually can be tested. In practice this was already
done but a lot of legacy code remained. In the past timing
happened to make it look like it was possible to test
Rizzo-Dungeon mitigation in more detail, but it was based on
false assumptions that can not be applied to streams.
|
|
It looked like two messages was received in the "wrong" order,
cuasing the request_and_reply_plain test case tro fail (on
a windows machine).
On closer inspection, the reason was that an "unconditional"
receive was made when waiting for a (disconnect) callback.
But instead we received a secondary message. So, remove
the unconditional receive and instead introduce a timeout
(10 seconds).
|
|
It seems that the megaco_config process did not start (for
an unknown reason) and that resulted in a failed test case.
But starting the config process was not what the test case
was for, so it should have resulted in a skip.
Also, since we did not check the result of the config start,
we don't know why it failed.
So, move the start and stop of the megaco_config process
to the [init|end]_per_testcase function(s). If we fail to
start, then we skip (with a useful reason).
|
|
|
|
The socket acceptconn test case has been split into two,
one for UDP and one for TCP.
OTP-15904
|
|
* rickard/node-refc-tests-22:
Fix etp-ets-tables
Fix node refc test for free processes hanging around
Enhanced node refc bookkeeping
Fix node container refc tests of ETS
Fix node refc test of external data
Node container refc test for persistent terms
Include persistent term storage in node/dist refc check
Fix node refc test for system message queue
|
|
* peterdmv/ssl/fix-tls13-alpn:
ssl: Fix handling of ALPN in TLS 1.3
|
|
* ingela/ssl/restructure-tests:
ssl: Add API suites
ssl: Covered by property tests
ssl: Correct RSP/PSK and ALPN handling
ssl: Better grouping of test
|
|
|
|
|
|
|
|
|
|
|
|
* rickard/node-refc-tests-21:
Node container refc test for persistent terms
Include persistent term storage in node/dist refc check
Fix node refc test for system message queue
|
|
This is also an effort to group test cases better.
More such commits will follow.
|
|
|
|
|
|
* rickard/node-refc-tests-20:
Fix node refc test for system message queue
|
|
|
|
* kjell/stdlib/io_colums_io_rows/OTP-15959/ERL-717:
Fix io:columns() and io:rows() are not working from escripts bug
|
|
The load test suite did not properly handle attempts to
skip test cases. If we failed to start one of the slave
nodes for whatever reason (in this case we got a timeout),
this should not result in a failed test case as this is
out of the control of the test case. As it was, we *did*
try to issue a skip, but the "load controller" did not
detect it. It instead transformed it into a regular error.
|
|
|
|
Extention handling need some fixes to work
correctly for ALPN and SSL-3.0 only client/servers
do not support extensions
|
|
Regroup testes after functionality making it easier to
test all variants (all protocols, all cert types etc).
Also extend OpenSSL interop
|
|
Added two place holder test cases for the socket options error
and linger.
OTP-15904
|
