summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoe Birr-Pixton <jpixton@gmail.com>2024-09-20 12:38:17 +0100
committerJoe Birr-Pixton <jpixton@gmail.com>2024-09-20 12:24:51 +0000
commit4a00cf2841e8bdee20910b72432f9f604626ffda (patch)
tree937668951eaabd03692caf13cae7dac9e2e2209a
parentfa4242cafc8e6bb1abe8fcb5d336df6e2bfbba62 (diff)
Fix links in howto section of manual
-rw-r--r--rustls/src/manual/howto.rs26
1 files changed, 13 insertions, 13 deletions
diff --git a/rustls/src/manual/howto.rs b/rustls/src/manual/howto.rs
index 826f5a51..f3a8219c 100644
--- a/rustls/src/manual/howto.rs
+++ b/rustls/src/manual/howto.rs
@@ -17,21 +17,21 @@ It's a TODO to make these and other extension points async.)
Once you have these two pieces, configuring a server to use them involves, briefly:
-- packaging your `sign::SigningKey` with the matching certificate chain into a [`sign::CertifiedKey`][certified_key]
-- making a [`ResolvesServerCertUsingSni`][cert_using_sni] and feeding in your `sign::CertifiedKey` for all SNI hostnames you want to use it for,
+- packaging your [`sign::SigningKey`][signing_key] with the matching certificate chain into a [`sign::CertifiedKey`][certified_key]
+- making a [`ResolvesServerCertUsingSni`][cert_using_sni] and feeding in your [`sign::CertifiedKey`][certified_key] for all SNI hostnames you want to use it for,
- setting that as your `ServerConfig`'s [`cert_resolver`][cert_resolver]
-For a complete example of implementing a custom `sign::SigningKey` and `sign::Signer` see
-the [rustls-cng] crate.
-
-[signing_key]: ../../sign/trait.SigningKey.html
-[choose_scheme]: ../../sign/trait.SigningKey.html#tymethod.choose_scheme
-[sig_scheme]: ../../enum.SignatureScheme.html
-[signer]: ../../sign/trait.Signer.html
-[sign_method]: ../../sign/trait.Signer.html#tymethod.sign
-[certified_key]: ../../sign/struct.CertifiedKey.html
-[cert_using_sni]: ../../struct.ResolvesServerCertUsingSni.html
-[cert_resolver]: ../../struct.ServerConfig.html#structfield.cert_resolver
+For a complete example of implementing a custom [`sign::SigningKey`][signing_key]
+and [`sign::Signer`][signer] see the [rustls-cng] crate.
+
+[signing_key]: crate::crypto::signer::SigningKey
+[choose_scheme]: crate::crypto::signer::SigningKey.choose_scheme()
+[sig_scheme]: crate::SignatureScheme
+[signer]: crate::crypto::signer::Signer
+[sign_method]: crate::crypto::Signer.sign()
+[certified_key]: crate::crypto::signer::CertifiedKey
+[cert_using_sni]: crate::server::ResolvesServerCertUsingSni
+[cert_resolver]: crate::ServerConfig::cert_resolver
[rustls-cng]: https://github.com/rustls/rustls-cng/blob/dev/src/signer.rs
[^1]: For PKCS#8 it does not support password encryption -- there's not a meaningful threat