Skip to content

let's enable vTLS 1.3#654

Closed
kinjelom wants to merge 1 commit intocloudfoundry:masterfrom
kinjelom:patch-1
Closed

let's enable vTLS 1.3#654
kinjelom wants to merge 1 commit intocloudfoundry:masterfrom
kinjelom:patch-1

Conversation

@kinjelom
Copy link
Copy Markdown
Contributor

Now, there is no way to enable TLS v1.3, let's enable TLS v1.3.

Now, there is no way to enable TLS v1.3, let's enable TLS v1.3.
@kinjelom kinjelom requested a review from CFN-CI as a code owner April 22, 2024 12:01
@kinjelom kinjelom requested a review from a team April 22, 2024 12:01
@maxmoehl
Copy link
Copy Markdown
Member

Could you please explain your change? I don't see how this changes anything related to TLSv1.3.

@domdom82
Copy link
Copy Markdown
Contributor

sslv3 is not TLSv1.3. More like TLSv1.0

@kinjelom
Copy link
Copy Markdown
Contributor Author

I'm sorry, my mistake - TLS v1.3 probably doesn't work due to the OpenSSL version in the stemcell.

@kinjelom kinjelom closed this Apr 22, 2024
@maxmoehl
Copy link
Copy Markdown
Member

It does work, but it is disabled by default. In our internal backlog we have a item to deprecate the individual no-* options in favour of exposing ssl-min-ver and ssl-max-ver. We are currently using the raw blocks to set those but this should really be a feature of the release.

ssl-max-ver
The default value is "TLSv1.2".

So if you are interested, feel free to contribute a PR :)

PS: I have it on my list to look into your other PR, but I have a lot on the table right now :/

@kinjelom
Copy link
Copy Markdown
Contributor Author

kinjelom commented Apr 23, 2024

ssl-min/max-ver

@maxmoehl done: #657

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants