64d110f19d
This commit adds a check that ./testssl.sh has both read and execute permission. If ./testssl.sh is lacking execute permission, it will pass the tests in 00_testssl_help.t and 01_testssl_banner.t that run the program as `bash ./testssl.sh`, but will fail the subsequent tests that run the program as `./testssl.sh`, but the reason for the failure will not be clear. |
||
---|---|---|
.. | ||
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 | ||
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 |
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.