Open dgryski opened 6 years ago
cc @FiloSottile
Change https://golang.org/cl/170701 mentions this issue: crypto/tls: fix a minor MAC vs padding leak
Change https://golang.org/cl/170704 mentions this issue: crypto/tls: implement full Lucky13 countermeasures for SHA-1 CBC ciphers
Change https://golang.org/cl/170702 mentions this issue: crypto/tls: avoid cache-based side channels in extracting the remote MAC
Change https://golang.org/cl/170703 mentions this issue: crypto/sha1: add ConstantTimeSumWithData
@FiloSottile Is there more to do here for 1.14?
Kindly ping @FiloSottile @katiehockman, shall we move this issue back to backlog, or is there something left for Go1.14 and then we can close it?
Since we're in the freeze and the RC1 has been cut, I think we should move this to the 1.15 milestone. @FiloSottile what do you think? It looks like you gave a +2 to one of the CLs early last year.
Punting to Go1.16 as no movement on the CLs since April 2019.
Punting to Go1.17.
Moving to Backlog.
As detailed in the paper "Pseudo Constant Time Implementations of TLS Are Only Pseudo Secure" https://eprint.iacr.org/2018/747