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

Enable .NET analyzers for all projects #1414

Merged
merged 6 commits into from
Jun 5, 2021
Merged

Enable .NET analyzers for all projects #1414

merged 6 commits into from
Jun 5, 2021

Conversation

mregen
Copy link
Contributor

@mregen mregen commented May 30, 2021

  • fix new warnings

@mregen mregen requested a review from AlinMoldovean May 30, 2021 08:22
@@ -234,7 +234,7 @@ public void Start()
httpsOptions.CheckCertificateRevocation = false;
httpsOptions.ClientCertificateMode = ClientCertificateMode.NoCertificate;
httpsOptions.ServerCertificate = m_serverCert;
httpsOptions.SslProtocols = SslProtocols.Tls | SslProtocols.Tls11 | SslProtocols.Tls12;
httpsOptions.SslProtocols = SslProtocols.None;
Copy link
Contributor

Choose a reason for hiding this comment

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

This is a functional change from Tlx|Tls11|Tls12 to None, what is the rational behind?

Copy link
Contributor

Choose a reason for hiding this comment

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

I think that setting "SslProtocols = SslProtocols.None" will allow the OS to chose the best protocol to use.
But maybe Martin can confirm...

Copy link
Contributor Author

Choose a reason for hiding this comment

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

exactly, Tls 1.1 etc should not be used anymore

@mregen mregen merged commit 9923141 into master Jun 5, 2021
@mregen mregen deleted the warnings branch June 5, 2021 05:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants