eccf90a534
The singular purpose of this crate should be to integrate Tokio and Rustls. Therefore, any feature that isn't about making Rustls work nicely with Tokio should be assumed a priori to be out of scope. In particular, it is out of scope for tokio-rustls to provide APIs to control SNI behavior. Instead, the application should configure Rustls's SNI behavior using Rustls's configuration APIs, and pass the configuration to tokio-rustls. Similarly, it is out of scope for tokio-rustls to provide APIs to control the certificate validation behavior. Instead, the application should configure certificate validation using Rustls's APIs. Perhaps there should be a crate that makes it convenient to do "dangerous" certificate validation, but IMO that shouldn't be tokio-rustls, but a different one. FWIW, the `danger` API was inherited from tokio-tls, and I'm working on making an analogous change there.
30 lines
809 B
TOML
30 lines
809 B
TOML
[package]
|
|
name = "tokio-rustls"
|
|
version = "0.3.1"
|
|
authors = ["quininer kel <quininer@live.com>"]
|
|
license = "MIT/Apache-2.0"
|
|
repository = "https://github.com/quininer/tokio-rustls"
|
|
homepage = "https://github.com/quininer/tokio-rustls"
|
|
documentation = "https://docs.rs/tokio-rustls"
|
|
readme = "README.md"
|
|
description = "Asynchronous TLS/SSL streams for Tokio using Rustls."
|
|
categories = ["asynchronous", "cryptography", "network-programming"]
|
|
|
|
[badges]
|
|
travis-ci = { repository = "quininer/tokio-rustls" }
|
|
appveyor = { repository = "quininer/tokio-rustls" }
|
|
|
|
[dependencies]
|
|
futures = "0.1"
|
|
tokio-io = "0.1"
|
|
rustls = "0.10"
|
|
tokio-proto = { version = "0.1", optional = true }
|
|
|
|
[dev-dependencies]
|
|
tokio-core = "0.1"
|
|
clap = "2.20"
|
|
webpki-roots = "0.12"
|
|
|
|
[target.'cfg(unix)'.dev-dependencies]
|
|
tokio-file-unix = "0.4"
|