The SIKE specifications document (by many authors) is going to be made public soon (either by us or NIST, @DemocraticLuntz... whoever does it first).
Show this thread
SIDH version 3.0, including our new key encapsulation protocol "SIKE", is now available via GitHub:https://github.com/Microsoft/PQCrypto-SIDH …
-
-
Thanks. Twitter will use this info to make your timeline better. Undo
-
-
-
I'll talk about our recent work on supersingular isogeny crypto at Real World Crypto in Zurich: https://rwc.iacr.org/2018/program.html …
#RWC2018#SIKE#SIDHShow this threadThanks. Twitter will use this info to make your timeline better. Undo
-
-
-
Are the p503 public keys smaller?
-
Smaller p, smaller key size, less security
-
Yep, this is supposed to be 128bit
-
Or more precisely, it is intended for matching the security of AES128. There are still too many open questions in quantum cryptanalysis. But, if isogenies stand the pass of time, there is a chance that p503 will become the most attractive option for most applications.
-
There is a lot to love about SIKEp503: speed, code simplicity and compactness, security against active attackers, and the smallest public keys in the PQ world, only 378 bytes w/o compression.
-
Wait, isn't AES128 64bit security against Grover?
-
Quantum sec. appears to be more complicated than simply applying Grover directly. As preliminary analysis, NIST is considering not only quantum circuit size but also circuit depth (limitation in running time on a quantum circuit). Check out Section 4.A.5, https://csrc.nist.gov/CSRC/media/Projects/Post-Quantum-Cryptography/documents/call-for-proposals-final-dec-2016.pdf …
-
OK, thanks!
End of conversation
New conversation -
-
-
How fast is SIDH over p503?
-
10 milliseconds (KEM encapsulation + KEM decapsulation) on my 3.4GHz Intel Skylake machine.
-
Same timing for SIDHp503 (10 msec., full ephemeral kex).
-
Excellent.
End of conversation
New conversation -
-
Hi Patrick, I found a minor “issue” in SIKEp751/ec isogeny, generic impl. Ping me for details/contact.
-
(correction, the bug affects all implementations, I sent you an email)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.