Skip to content
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

tls: Disable clientsessioncache #234

Merged
merged 1 commit into from
Apr 12, 2023

Conversation

MathieuBordere
Copy link
Contributor

The ClientCessionCache causes incompatibilities between go-dqlite 1.11.6 and 1.11.7.

go-dqlite 1.11.7 contains a new SimpleTLSConfig that eliminated incompatibilities with go 1.19.6 and newer. However, it seems nodes running go-dqlite versions older than 1.11.7 throw TLS errors when communication with modern nodes if the ClientCessionCache is enabled.

So, disable the ClientCessionCache by default. Users can still opt to enable it by adapting the client config returned by SimpleTLSConfig.

The ClientCessionCache causes incompatibilities between go-dqlite
1.11.6 and 1.11.7.

go-dqlite 1.11.7 contains a new SimpleTLSConfig that eliminated
incompatibilities with go 1.19.6 and newer. However, it seems nodes
running go-dqlite versions older than 1.11.7 throw TLS errors when
communication with modern nodes if the ClientCessionCache is enabled.

So, disable the ClientCessionCache by default. Users can still opt to
enable it by adapting the client config returned by SimpleTLSConfig.

Signed-off-by: Mathieu Borderé <mathieu.bordere@canonical.com>
@MathieuBordere MathieuBordere marked this pull request as draft March 17, 2023 10:44
@MathieuBordere
Copy link
Contributor Author

I'll wait for some user feedback and write a test in meanwhile.

@MathieuBordere MathieuBordere marked this pull request as ready for review April 12, 2023 14:16
@MathieuBordere MathieuBordere merged commit 3aae619 into canonical:master Apr 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants