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

Update safely a certificate pool with GetConfigForClient #23

Closed
maraino opened this issue Jan 11, 2019 · 2 comments
Closed

Update safely a certificate pool with GetConfigForClient #23

maraino opened this issue Jan 11, 2019 · 2 comments
Assignees

Comments

@maraino
Copy link
Contributor

maraino commented Jan 11, 2019

The SDK does not remove the old roots as it's not possible to safely change the RootCAs/ClientCAs directly on the tls.Config. But tls.Config method GetConfigForClient allows to get a custom tls.Config after a ClientHello. More information:
https://tip.golang.org/pkg/crypto/tls/#Config.GetConfigForClient
https://diogomonica.com/2017/01/11/hitless-tls-certificate-rotation-in-go/

@maraino maraino self-assigned this Jan 11, 2019
@maraino
Copy link
Contributor Author

maraino commented Jan 22, 2019

We can do this safely for a server but not for a client.
Waiting for golang/go#22836 to be implemented

@dopey
Copy link
Contributor

dopey commented Feb 7, 2019

In v0.8.3 we released features that enabled root rotation and CA cross federation. In v0.8.4 we're releasing enhancements that allow clients and servers in the Golang SDK to automatically update the Root and Client CA Certificates in their TLSConfig when they renew their Certificates with the step Certificate Authority. Clients and Servers running the updated version will continuously stay up to date with Root and Federation changes applied in the step CA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants