Remember that P-256 carry bug a while back from @FiloSottile/@thecomp1ler/@Cloudflare ?
Here's the bug: https://github.com/golang/go/issues/20040 …
And here's what happen when you get a single bit wrong in a crypto algorithm: https://events.ccc.de/congress/2017/Fahrplan/events/9021.html …
"You must use one of a small # of bleeding-edge ISAs to do crypto safely" is not something I consider a viable position.
-
-
Fair enough, I can respect that. For me, “all crypto opts must take the maximum theoretical execution time on my device” is not a viable position either.
-
I actually have alternate possible solutions based on pseudo-const-time vm interp & const-time algorithms inside the vm, but also very costly.
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.