Skip to content

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

Merged
merged 1 commit into from
Oct 31, 2018
Merged

Update native-tls and tokio-tls #186

merged 1 commit into from
Oct 31, 2018

Conversation

mati865
Copy link
Contributor

@mati865 mati865 commented Sep 14, 2018

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:

warning: use of deprecated item 'tokio_io::AsyncRead::framed': Use tokio_codec::Decoder::framed instead
   --> src/server/upgrade/async.rs:221:5
    |
221 |             .framed(HttpServerCodec)
    |  

But I couldn't manage to fix them.

Copy link
Member

@vi vi left a 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()))
Copy link
Member

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Docs say so and connector is converted to tokio-tls type above.

@vi
Copy link
Member

vi commented Sep 23, 2018

Which version should it be after this pull request: 0.20.4 or 0.21.0?

@mati865
Copy link
Contributor Author

mati865 commented Sep 23, 2018

Which version should it be after this pull request: 0.20.4 or 0.21.0?

It requires upgrading native-tls from 0.1 to 0.2 to work so I think it's breaking change.

@mati865
Copy link
Contributor Author

mati865 commented Oct 12, 2018

Ping

@vi
Copy link
Member

vi commented Oct 12, 2018

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.

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