From cc2bf6ebabc910a07942abb394013cbea8e70990 Mon Sep 17 00:00:00 2001
From: zzz <zzz@mail.i2p>
Date: Tue, 21 May 2019 18:46:14 +0000
Subject: [PATCH] references
---
i2p2www/spec/proposals/151-ecdsa-blinding.rst | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/i2p2www/spec/proposals/151-ecdsa-blinding.rst b/i2p2www/spec/proposals/151-ecdsa-blinding.rst
index 48c439b85..86bf5bb7c 100644
--- a/i2p2www/spec/proposals/151-ecdsa-blinding.rst
+++ b/i2p2www/spec/proposals/151-ecdsa-blinding.rst
@@ -72,8 +72,8 @@ HKDF(salt, ikm, info, n)
of length 32 bytes, and a context-specific 'info' value, and produces an output
of n bytes suitable for use as key material.
- Use HKDF as specified in [RFC-5869], using the HMAC hash function SHA-256
- as specified in [RFC-2104]. This means that SALT_LEN is 32 bytes max.
+ Use HKDF as specified in [RFC-5869]_, using the HMAC hash function SHA-256
+ as specified in [RFC-2104]_. This means that SALT_LEN is 32 bytes max.
Blinding Calculations
@@ -140,3 +140,11 @@ ECDSA's public key is (X,Y) pair, so for P256, for example, it's 64 bytes, rathe
Either b33 address will be longer, or public key can be stored in compressed format like in bitcoin wallets.
+References
+==========
+
+.. [RFC-2104]
+ https://tools.ietf.org/html/rfc2104
+
+.. [RFC-5869]
+ https://tools.ietf.org/html/rfc5869
--
GitLab