diff options
Diffstat (limited to 'spec/dir-spec/converting-curve25519-public-key-to-ed25519-public.md')
| -rw-r--r-- | spec/dir-spec/converting-curve25519-public-key-to-ed25519-public.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/spec/dir-spec/converting-curve25519-public-key-to-ed25519-public.md b/spec/dir-spec/converting-curve25519-public-key-to-ed25519-public.md index a676228..57f9d1d 100644 --- a/spec/dir-spec/converting-curve25519-public-key-to-ed25519-public.md +++ b/spec/dir-spec/converting-curve25519-public-key-to-ed25519-public.md @@ -45,8 +45,8 @@ To get the sign, the easiest way is to take the corresponding private key, feed it to the ed25519 public key generation algorithm, and see what the sign is. -[Recomputing the sign bit from the private key every time sounds -rather strange and inefficient to me… —isis] +\[Recomputing the sign bit from the private key every time sounds +rather strange and inefficient to me… —isis\] Note that in addition to its coordinates, an expanded Ed25519 private key also has a 32-byte random value, "prefix", used to compute internal `r` @@ -55,7 +55,7 @@ derived deterministically from the curve25519 key. The Tor implementation derives it as `SHA512(private_key | STR)[0..32]`, where STR is the nul-terminated string: -"Derive high part of ed25519 key from curve25519 key\0" +"Derive high part of ed25519 key from curve25519 key\\0" On the client side, where there is no access to the curve25519 private keys, one may use the curve25519 public key's Montgomery u-coordinate to |