I misinterpreted the second return parameter of boring.GenerateKeyECDH. It is meant to contain the private bytes of the key, but we are returning the public bytes. We haven't found this mismatch until now because boring support for ECDH landed just 4 days ago in CL 423363.
This PR updates GenerateKeyECDH so it matches upstream behavior.
I misinterpreted the second return parameter of boring.GenerateKeyECDH. It is meant to contain the private bytes of the key, but we are returning the public bytes. We haven't found this mismatch until now because boring support for ECDH landed just 4 days ago in CL 423363.
This PR updates
GenerateKeyECDH
so it matches upstream behavior.