From 8abe2b1e93d18a2815150a50d0c9723112ea25d9f1127f9794954ea134f0e934 Mon Sep 17 00:00:00 2001 From: Mars Ultor Date: Sat, 19 Apr 2025 15:40:06 -0500 Subject: [PATCH] notes redo --- notes.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/notes.md b/notes.md index 68a6a36..6cf7898 100644 --- a/notes.md +++ b/notes.md @@ -65,15 +65,15 @@ Your proposed authentication flow is on the right track, but there are a few opt This approach gives you extremely high security while maintaining reasonable performance characteristics, especially with the optimization of having the client identify itself rather than the server trying all possible public keys. # docs -[](https://docs.rs/x25519-dalek/latest/x25519_dalek/) +[x25519_dalek](https://docs.rs/x25519-dalek/latest/x25519_dalek/) -[](https://docs.rs/rsa/latest/rsa/) +[rsa](https://docs.rs/rsa/latest/rsa/) -[](https://docs.rs/aes-gcm/latest/aes_gcm/) +[aes-gcm](https://docs.rs/aes-gcm/latest/aes_gcm/) -[](https://docs.rs/hkdf/latest/hkdf/) +[hkdf](https://docs.rs/hkdf/latest/hkdf/) -[](https://docs.rs/zeroize/latest/zeroize/) +[zeroize](https://docs.rs/zeroize/latest/zeroize/) -[](https://docs.rs/sha2/latest/sha2/) +[sha2](https://docs.rs/sha2/latest/sha2/)