Skip to content

Allow OS to choose the best protocol to use#547

Open
lwalejko wants to merge 1 commit into
sta:masterfrom
lwalejko:change-default-ssl-protocol-to-more-secure-version
Open

Allow OS to choose the best protocol to use#547
lwalejko wants to merge 1 commit into
sta:masterfrom
lwalejko:change-default-ssl-protocol-to-more-secure-version

Conversation

@lwalejko

Copy link
Copy Markdown

As per documentation (https://docs.microsoft.com/en-us/dotnet/api/system.security.authentication.sslprotocols?view=netframework-4.8), None should be used as default value, not Default, because Default allows only outdated and less secure protocols.

…hat are not secure.

This setting is recommended by SslProtocols Enum documentation.
@lwalejko lwalejko marked this pull request as ready for review June 21, 2019 09:36

@eynzhang eynzhang left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I agree with this as I encountered same issue when initializing the connection, and I found the same root cause while looking at the source code.

@lwalejko

lwalejko commented Dec 10, 2019

Copy link
Copy Markdown
Author

I forgot about this pull request to be honest ;)

@eynzhang have you tried if this change works for you as intended? I had some more problems with this and ended up using System.Security.Authentication.SslProtocols.Tls12 value directly.

@eynzhang

Copy link
Copy Markdown

I think that’s depends on the settings in server, in my cases ‘None’ is working for me.

That’s why I proposed a request on the readme document here:
#583

Maybe a better way is to pass this property by the constructor or a public method.

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.

2 participants