-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Close TLS and QUIC links on certificate expiration #1564
Close TLS and QUIC links on certificate expiration #1564
Conversation
PR missing one of the required labels: {'bug', 'dependencies', 'documentation', 'breaking-change', 'new feature', 'enhancement', 'internal'} |
716f7ae
to
65d3b41
Compare
Commit efb6cb931fa34ab9ab2df5d4912390684c539432 changes the approach to one expiration task per link instance, as the previous implementation had a design flaw where Expiration tasks are relatively low in cost as they |
…le termination of expiration_task
In cb0d6c4 I reworked the implementation to dodge the performance issues of |
Quic and TLS links currently do not close when remote certificate expires. This PR makes instances monitor the expiration of the remote certificate chain, closing the link at the moment of expiration.
This is configurable via the
transport.link.tls.close_link_on_expiration
key in the config file. It is set by default tofalse
to maintain the old behavior as default.