Store WebRTC Direct certificate in the keychain #2988
Labels
good first issue
Good issue for new contributors
help wanted
Seeking public contribution on this issue
kind/enhancement
A net-new feature or improvement to an existing feature
We generate a new TLS certificate for the WebRTC Direct transport on startup. This means our multiaddr changes between reboots even though the port/peer id might remain the same.
Instead we should store it in the keychain and re-use it if it exists and the expiry is within some configurable threshold.
This way previously shared multiaddrs would still be valid.
The text was updated successfully, but these errors were encountered: