Certificate expiry

Summary

As self-signed WebRTC certificates expire after 30 days, the rust peer should generate a new certificate once the old one has expired.

Expected behavior

The rust peer should, when loading an expired certificate, automatically detect that it is no longer valid and instead generate and advertise (and locally save) a new certificate.

Actual behavior

The peer seems to keep using and advertising the expired certificate in the peer address, which leads to unsuccessful connection attempts by other peers that rely on WebRTC.

Relevant log output

No response

Possible Solution

I was unable to find a programmatic way of detecting the certificate's expiry date in rust-libp2p. If this could be done, then regenerating and saving a new certificate should be trivial.

Version

No response

Would you like to work on fixing this bug ?

Yes

Start by tracing how the Rust peer loads, saves, and advertises its self-signed WebRTC certificate, then determine how certificate expiry can be detected. Done means an expired certificate is replaced with a newly generated one that is saved locally and advertised to peers.