tls-async
| Crates.io | tls-async |
| lib.rs | tls-async |
| version | 0.3.0-alpha.7 |
| source | src |
| created_at | 2019-01-22 20:47:36.388919 |
| updated_at | 2019-06-06 17:54:02.978081 |
| description | TLS support for AsyncRead/AsyncWrite using native-tls |
| homepage | |
| repository | https://github.com/dbcfd/tls-async |
| max_upload_size | |
| id | 110079 |
| size | 62,884 |
Danny Browning (dbcfd)
documentation
README
tls-async
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
Usage
First, add this to your Cargo.toml:
[dependencies]
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:
- On Windows, SChannel is used
- On OSX, SecureTransport is used
- Everywhere else, OpenSSL is used
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.
License
This project is licensed under the MIT license.
Contribution
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.