Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Return 0 for SSL_OP_NO_TLSv1_3 when TLSv1.3 is not supported. #392

Merged
merged 1 commit into from Sep 23, 2018

Conversation

normanmaurer
Copy link
Member

Motivation:

We need to use 0 for SSL_OP_NO_TLSv1_3 when TLSv1.3 is not supported to not disable any protocols by mistake when its not supported at all.

Modifications:

Define SSL_OP_NO_TLSv1_3 as 0 when TLSv1.3 is not supported.

Result:

Correctly handle the case when TLSv1.3 is not supported and so be able to use it in this case.

Motivation:

We need to use 0 for SSL_OP_NO_TLSv1_3 when TLSv1.3 is not supported to not disable any protocols by mistake when its not supported at all.

Modifications:

Define SSL_OP_NO_TLSv1_3 as 0 when TLSv1.3 is not supported.

Result:

Correctly handle the case when TLSv1.3 is not supported and so be able to use it in this case.
@normanmaurer
Copy link
Member Author

I messed this one up ... We need this to be able to correctly handle both cases: when TLSv1.3 is supported and if its not supported.

@normanmaurer normanmaurer added this to the 2.0.17.Final milestone Sep 22, 2018
@normanmaurer
Copy link
Member Author

Once this is merged I will cut a release.

@normanmaurer
Copy link
Member Author

@netty-bot test this please

@normanmaurer normanmaurer self-assigned this Sep 22, 2018
@normanmaurer
Copy link
Member Author

@netty-bot test this please

Copy link
Member

@carl-mastrangelo carl-mastrangelo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@normanmaurer normanmaurer merged commit bc16a45 into master Sep 23, 2018
@normanmaurer normanmaurer deleted the no_tls13_supported branch September 23, 2018 02:08
fzakaria pushed a commit to fzakaria/netty-tcnative that referenced this pull request Feb 4, 2019
)

Motivation:

We need to use 0 for SSL_OP_NO_TLSv1_3 when TLSv1.3 is not supported to not disable any protocols by mistake when its not supported at all.

Modifications:

Define SSL_OP_NO_TLSv1_3 as 0 when TLSv1.3 is not supported.

Result:

Correctly handle the case when TLSv1.3 is not supported and so be able to use it in this case.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants