Add a CI workflow for no-tls1_2 no-tls1_3 - #18188
bernd-edlinger wants to merge 19 commits into
Conversation
|
I've fixed two test failures that I already knew how to fix, because they were also in 1.1.1, |
|
Hmm, that is strange, when configured with vs. @mattcaswell is that expected? |
|
You would need |
|
Ah, of course... |
|
That's A LOT better now: |
a07f686 to
ed504d2
Compare
494d729 to
8192e89
Compare
|
Well, it's getting better: |
|
I still wonder whether all this effort is worth it. Would it make more sense |
|
It works now, so no longer WIP. See also #18252 for the 1.1.1 variant of this PR. |
50714b1 to
ada8859
Compare
I had to re-base the PR because of a merge conflict in test/ssl-tests/12-ct.cnf
|
So while the change in test/ssl-tests/12-ct.cnf is no longer necessary |
41d46b7 to
f1f2330
Compare
This test needs security level 0.
In order to create a SSL connection with TLS<1.2 we need security level 0.
This test needs -cipher DEFAULT@SECLEVEL=0 to work in that configuration.
Lots of test cases use this proxy and fail, because the security level needs to be adjusted to use @SECLEVEL=0 in this configutation.
This needs en explicit @SECLEVEL=0 in the ciphers string when neither tls1_2 nor tls1_3 are configured.
When tls1_2 and tls1_3 are both disabled and the test does not define an explicit CipherString, use "DEFAULT\@SECLEVEL=0" instead of "DEFAULT".
When tls1_2 is not available this test needs @SECLEVEL=0.
When tls1_2 is not available this test needs @SECLEVEL=0.
There are a couple changes necessary here, mostly adjusting security level.
When only TLS<1.2 is available and the security level is 0, SSL_get1_supported_ciphers(ssl) retuns NULL. That changed with commit 7bf2e4d. Not sure of that is a bug or a feature, especially since that does not happen with no-tls1_2 no-ec no-dh. Test the current behaviour in case it changes again, so we will know.
The new test using rsa-pss fails if neither tls1_2 nor tls1_3 is available.
4cf6dc0 to
35288d4
Compare
|
removed the no-dtls1_2 fix from this PR since I found that #18848 |
|
This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago |
|
This PR is in a state where it requires action by @openssl/committers but the last update was 61 days ago |
|
This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago |
|
This PR is in a state where it requires action by @openssl/committers but the last update was 61 days ago |
|
This PR is in a state where it requires action by @openssl/committers but the last update was 92 days ago |
|
This PR is in a state where it requires action by @openssl/committers but the last update was 123 days ago |
|
This PR is in a state where it requires action by @openssl/committers but the last update was 154 days ago |
|
This PR is in a state where it requires action by @openssl/committers but the last update was 185 days ago |
|
This PR is in a state where it requires action by @openssl/committers but the last update was 216 days ago |
|
This PR is in a state where it requires action by @openssl/committers but the last update was 247 days ago |
|
So I'm happy to review this, but it seems there are conflicts, and it's been left so long that "2022" is no longer the current year for copyright lines. @bernd-edlinger will you update this, or have you lost interest? |
|
This PR is waiting for the creator to make requested changes but it has not been updated for 30 days. If you have made changes or commented to the reviewer please make sure you re-request a review (see icon in the 'reviewers' section). |
|
This PR is waiting for the creator to make requested changes but it has not been updated for 61 days. If you have made changes or commented to the reviewer please make sure you re-request a review (see icon in the 'reviewers' section). |
|
This PR has been closed. It was waiting for the creator to make requested changes but it has not been updated for 90 days. |
Currently this configuration seems to be failing several tests.
Checklist