Some TLS toolkits export a result that can be checked afterwards even if
the TLS negotation returned successfully. This can be used for example
if you disabled certificate checks by default, but then want to check
the outcome.
Currently this is only supported on boring TLS.
Add a method that, when using a TLS toolkit that supports it, returns
the entire certificate chain. This is useful, for example, when
implementing DANE support which has directives that apply to the issuer
and not just to the leaf certificate.
Not all TLS toolkits support this, so the code will panic if the method
is called when using a TLS toolkit that has no way to return these
certificates.
In contexts where FIPS certification is mandatory, having the
ability to use the certified boring TLS library is sometimes necessary.
Added initial support for it, only one TLS toolkit can be enabled at
one time.
This adds a `local_address: Option<IpAddr>` parameter to the synchronous, and tokio connect functions.
(As far as I can see there is no current way to support this in async-std, because the library doesn't provide any way to do an async connect for an existing socket)
* Update dependencies (#386)
* Update dependencies and set MSRV to 1.40
* update hyperx
* Use display instead of description for errors
* Make hostname an optional feature
* Envelope from headers
* Update hyperx to 1.0
* rename builder to message
* Cleanup and make Transport send Messages
* Update rustls from 0.16 to 0.17
* Move transports into a common folder
* Merge imports from same crate
* Add message creation example to the site
* Hide "extern crate" in doc examples
* Add References and In-Reply-To methods
* Add message-id header
* Add blog posts and improve doc examples
Change the default authentication mechanism selection check if the
connection is encrypted, and only test PLAIN when it is the case.
Also make the .authentication_mechnaism only take one mechanism, as
a user will specify it he wants to ensure one particular method will
be used.
Closes#65
