-
Notifications
You must be signed in to change notification settings - Fork 226
Update native-tls and tokio-tls #186
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks generally OK, not checked the details or tried to build it yet...
Err(e) => return Box::new(future::err(e)), | ||
} | ||
}; | ||
// secure connection, wrap with ssl | ||
let future = tcp_stream | ||
.map_err(|e| e.into()) | ||
.and_then(move |s| connector.connect_async(&host, s).map_err(|e| e.into())) | ||
.and_then(move |s| connector.connect(&host, s).map_err(|e| e.into())) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it still async connect, not the blocking version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which version should it be after this pull request: |
It requires upgrading |
Ping |
I have a reminder to check accumulated pull requests and make a rust-websocket release in 20 days, in case of inactivity of original developers of rust-websocket. |
Native-tls 0.1 uses outdated
openssl
crate that doesn't build with OpenSSL 1.1.1 (Arch Linux is already using it and openSUSE Tumbleweed will update in a few days).Updating native-tls also fixes few issues with static OpenSSL builds.
It throws warnings like:
But I couldn't manage to fix them.