You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To clarify this scary sounding issue, @Stebalien is talking about the LocalPrivateKey method on the secureConn type that returns the private key we are using for the encrypted channel. Its not (as one might assume by reading the title) leaking private key data over the network in any way.
Stebalien
changed the title
Consider not exposing private keys on secure connections
Consider removing the LocalPrivateKey method from secure connections
Mar 8, 2018
marten-seemann
changed the title
Consider removing the LocalPrivateKey method from secure connections
core: consider removing the LocalPrivateKey method from secure connections
Aug 19, 2022
It's really not necessary and generally not a good idea to expose private keys like this.
The text was updated successfully, but these errors were encountered: