otrv4 / ed448 Goto Github PK

https://github.com/armfazh/redox-ecc/

• CondSwap
• Lookup
• Insert
• Mask
• Select

It seems https://github.com/awnumar/memguard might help us deal with buffers and so on of data that we will need to be careful with, and wipe. This is not perfect, but might be better than not doing anything.

otrv4/ed448 public key size is 56 bytes, private key size is 144 bytes, signature is 112 bytes

According the rfc8032 standard: https://tools.ietf.org/html/rfc8032

4. EdDSA uses small public keys (32 or 57 bytes) and signatures (64 or 114 bytes) for Ed25519 and Ed448, respectively;

Why are pub/priv/sig sizes for otrv4/ed448 are so different from a rfc8032 standard?
What standard does otrv4/ed448 implementation follow?

In accordance with Mike Hamburg's paper.

• implement bigNumber arithmetic // merged
• implement the 3 decaf new functions: equality, encoding and decoding // merged
• implement the new scalar operations
• implement the new point operations // check if all are done
• change the point representation: projective coordinates
• implement a generator for the base point according to the new coordinates // this should be on otr4
• implement elligator2
• implement montgomery mul and use it on 'decode_long'

See: https://en.wikipedia.org/wiki/Jacobian_curve