fix: added tls1.0/1.1 patch for openssl when using older tls versions… #6105
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contribution Guidelines
What does this PR include?
Short Description
This PR includes a fix stated in: https://community.mailcow.email/d/4062-hi-all/20 to fix the openssl 3.0 lack of tls1.X support which has been deactivated by default.
Affected Containers
Did you run tests?
What did you tested?
I tested the changes by modifying the extra.cf for both containers to readd tls1.0/1.1 support (like described in the docs).
I've checked that the openssl.conf got modified with the patch.
Then i tested if i can connect via openssl client from outside by using a TLS version of 1.0/1.1, previously it was not possible as the openssl from the container blocked those requests.
What were the final results? (Awaited, got)
The openssl.conf got modified as awaited and i was able to connect to the server by using TLS 1.0/1.1 again.