Re: Crypto friendly optimization?

For the Go programming language there has been discussion of adding a
secret.Do function, that invokes a function closure and, after it returns,
erases all memory that it allocated. The goal is better, though not perfect,
forward secrecy, so that people can't capture a key today and a conversation
today and, if they key becomes vulnerable, later use it to decrypt the
conversation. There is a lot of discussion at <https://go.dev/issue/21865>
with the output at
<https://github.com/golang/go/issues/21865#issuecomment-925310304>. This is
not yet implemented, but the current attempts require work in both the
compiler and the runtime library.


Related to that is a more speculative idea to enable ARM DIT/Intel DOIT mode
while executing a function. Discussion at <https://go.dev/issue/66450>.


But there is no special work in the Go compilers to ensure that code written
to execute in constant-time is not optimized to run in non-constant-time. It
would be interesting to hear about other work in that area.




Ian

Return to the comp.compilers page.
Search the comp.compilers archives again.