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

Exposes SSL Stream and adds more TLS settings #132

Merged
merged 1 commit into from
Jun 16, 2016
Merged

Conversation

mtuchkov
Copy link
Contributor

Motivation:

Some important SSL Stream settings are hidden in the TlsHandler class

Modifications:
SSLStream is provided by user now via factory method;
TLS settings extended

Results:
More advanced scenarios, like X509 client authentication, are possible to do now

}

public static TlsHandler Client(string targetHost) => new TlsHandler(false, null, targetHost, null);
Copy link
Member

Choose a reason for hiding this comment

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

should we leave these for common cases and internalize sslStreamFactory in such a case?

@mtuchkov mtuchkov force-pushed the tlsconfig branch 3 times, most recently from 35053b7 to 0ff6120 Compare June 16, 2016 17:31
}

public ClientTlsSettings(bool checkCertificateRevocation, X509CertificateCollection certificates, string targetHost)
: this(SslProtocols.Tls | SslProtocols.Tls11 | SslProtocols.Tls12, checkCertificateRevocation, certificates, targetHost)
Copy link
Member

Choose a reason for hiding this comment

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

shall we remove TLS 1.0 from here by default as well already?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't want to do a breaking change. Let's do that in version 0.4.0

Motivation:

Some important SSL Stream settings are hidden in the TlsHandler class

Modifications:
SSLStream is provided by user now via factory method;
TLS settings extended

Results:
More advanced scenarios, like X509 client authentication, are possible to do now
@nayato
Copy link
Member

nayato commented Jun 16, 2016

lgtm

@nayato nayato merged commit fb18eaf into Azure:dev Jun 16, 2016
@nayato
Copy link
Member

nayato commented Jun 16, 2016

addresses #60

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.

3 participants