-
Notifications
You must be signed in to change notification settings - Fork 51
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
How to connect to SSL TCP sockets using a trusted certificate (not self signed?) #30
Comments
I tried it again with a different domain (letsencrypt cert this time around) and I have the same error. |
Try using the following code to create the configuration:
The default Configuration init method should not be used. In a future release of SSLService, this will be enforced. Re-open this issue if you still have the problem after making the change. Thanks. |
I just looked at it a bit more... There was a default constructor (due to improperly defaulting parameters) that was getting called. The change I suggested above will work for the current version however, in a future version (maybe later today), what you originally coded will work. Thanks for the find. I'm re-opening the issue pending the fix. |
The change above did indeed work for me. Thank you loads @billabt |
Glad the fix worked for you. It's now permanently fixed in 0.12.38. Using the default initializer will work as expected. Thanks again for finding this. |
I have a server to which I can connect using openssl as so:
and it establishes fine. The certificate is issued by Digicert.
How can I connect to this socket using
BlueSSLService
? I am using the follow codewhich fails with
The operation couldn’t be completed. (Socket.SSLError error 0.)
I can only find documentation for self signed certificates in the repo.
The text was updated successfully, but these errors were encountered: