pub struct TlsStreamBuilder { /* fields omitted */ }
A builder for the TlsStream
A builder for associating trust information to the TlsStream
.
Add a custom trusted peer certificate or certificate auhtority.
If this is the 'client' then the 'server' must have it associated as it's identity
, or have had the identity
signed by this
Creates a new TlsStream to the specified name_server
RFC 7858, DNS over TLS, May 2016
3.2. TLS Handshake and Authentication
Once the DNS client succeeds in connecting via TCP on the well-known
port for DNS over TLS, it proceeds with the TLS handshake [RFC5246],
following the best practices specified in [BCP195].
The client will then authenticate the server, if required. This
document does not propose new ideas for authentication. Depending on
the privacy profile in use (Section 4), the DNS client may choose not
to require authentication of the server, or it may make use of a
trusted Subject Public Key Info (SPKI) Fingerprint pin set.
After TLS negotiation completes, the connection will be encrypted and
is now protected from eavesdropping.
name_server
- IP and Port for the remote DNS resolver
dns_name
- The DNS name, Subject Public Key Info (SPKI) name, as associated to a certificate
Returns the "default value" for a type. Read more
🔬 This is a nightly-only experimental API. (try_from
)
The type returned in the event of a conversion error.
🔬 This is a nightly-only experimental API. (try_from
)
Immutably borrows from an owned value. Read more
Mutably borrows from an owned value. Read more
🔬 This is a nightly-only experimental API. (try_from
)
The type returned in the event of a conversion error.
🔬 This is a nightly-only experimental API. (try_from
)
🔬 This is a nightly-only experimental API. (get_type_id
)
this method will likely be replaced by an associated static