mirror of
https://github.com/drwetter/testssl.sh.git
synced 2025-01-30 20:31:15 +01:00
a499233df2
This adds a unit test to compare a run against google with the supplied openssl version vs /usr/bin/openssl . This would fix #2626. It looks like there are still points to clarify * NPN output is different (bug) * Newer openssl version claims it's ECDH 253 instead of ECDH 256. * Newer openssl version claims for 130x cipher it's ECDH 253, via sockets it´s ECDH/MLKEM. This seems a bug (@dcooper) A todo is also restricing the unit test to the one where openssl is being used. E.g. the ROBOT check and more aren't done with openssl. So there's no value checking this here. |
||
---|---|---|
.. | ||
baseline_data | ||
00_testssl_help.t | ||
01_testssl_banner.t | ||
02_clientsim_txt_parsable.t | ||
05_ca_hashes_up_to_date.t | ||
10_baseline_ipv4_http.t | ||
11_baseline_ipv6_http.t.DISABLED | ||
12_diff_opensslversions.t | ||
21_baseline_starttls.t | ||
23_client_simulation.t | ||
31_isJSON_valid.t | ||
32_isHTML_valid.t | ||
33_isJSON_severitylevel_valid.t | ||
51_badssl.com.t | ||
59_hpkp.t.tmpDISABLED | ||
61_diff_testsslsh.t | ||
Readme.md |
Naming scheme
- 00-05: Does the bare testssl.sh work at all?
- 10-29: Do scans work fine (client side)?
- 30-39: Does reporting work?
- 50-69: Are the results what I expect (server side)?
Please help to write Travis/CI tests! Documentation can be found here.
You can consult the existing code here. Feel free to use 10_baseline_ipv4_http.t
or 23_client_simulation.t
as a
template.