#tls #async #romio #compat

nightly tls-async

TLS support for AsyncRead/AsyncWrite using native-tls

7 releases

0.3.0-alpha.7 Jun 6, 2019
0.3.0-alpha.6 May 13, 2019
0.3.0-alpha.5 Apr 26, 2019
0.3.0-alpha.2 Feb 26, 2019
0.3.0-alpha.1 Jan 22, 2019

#1932 in Asynchronous

Download history 1/week @ 2023-11-13 16/week @ 2023-11-20 1/week @ 2023-11-27 14/week @ 2023-12-04 8/week @ 2023-12-11 14/week @ 2023-12-25 7/week @ 2024-01-01 1/week @ 2024-01-08 9/week @ 2024-01-15 12/week @ 2024-01-22 14/week @ 2024-01-29 34/week @ 2024-02-12 166/week @ 2024-02-19

215 downloads per month

MIT license

288 lines


build status crates.io version docs.rs docs MIT licensed

This is an experimental fork of tokio-tls on top of Futures 0.3 AsyncRead, AsyncWrite, and Compat. It is primarily intended for usage with Romio.

An implementation of TLS/SSL streams for Futures 0.3 built on top of the native-tls crate



First, add this to your Cargo.toml:

tls-async = "0.3.0-alpha.5"

Next, add this to your crate:

use tls_async::{TlsConnector, TlsAcceptor};

You can find few examples how to use this crate in tests directory.

By default the native-tls crate currently uses the "platform appropriate" backend for a TLS implementation. This means:

Typically these selections mean that you don't have to worry about a portability when using TLS, these libraries are all normally installed by default.


This project is licensed under the MIT license.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in tls-async by you, shall be licensed as MIT, without any additional terms or conditions.


~156K SLoC