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

container manager certificate is not regenerated if databox IP changes #331

Open
cgreenhalgh opened this issue Sep 4, 2019 · 0 comments

Comments

@cgreenhalgh
Copy link

(Databox 0.5.2)
The container-manager certificate is used by the databox HTTPS server. It includes the discovered IP addresses of the databox when generated.
It is only generated when the databox is first started and subsequently persisted. So if the databox changes IP (e.g. DHCP lease expires or moves to new network) then the IPs are wrong and HTTPS connection fails/is marked insecure (depending on browser).
While the root certificate should be regenerated (so it doesn't need to be reinstalled), this one should be if the databox IPs change.

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

No branches or pull requests

1 participant