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

(SUP-3714) check console cert for expiration #168

Closed
wants to merge 1 commit into from

Conversation

MartyEwings
Copy link
Collaborator

this commit checks the default location of the console cert and does the usual expiration check:

Flaws with this method:

console cert file may be present and not in use resulting in false readings

does not work if custom cert location exists

@MartyEwings MartyEwings requested a review from a team as a code owner October 14, 2022 10:25
@MartyEwings MartyEwings linked an issue Oct 14, 2022 that may be closed by this pull request
@MartyEwings
Copy link
Collaborator Author

MartyEwings commented Oct 14, 2022

This pr is to allow for collaboration, this method is filled with holes! and this one is actually harder than it looks

Ideally we would ask the server:

openssl s_client -servername localhost -connect localhost:443 2>/dev/null | openssl x509 -noout -dates

Except on FIPS we cant use the openssl client so that means we can-not do this.

Unless we skip on FIPS enabled systems?

@MartyEwings
Copy link
Collaborator Author

Hmm unless we use the ruby library for the remote connection, maybe it will work the same way it allows for static file parsing

@jarretlavallee
Copy link
Contributor

We can get the location of the SSL cert from /etc/puppetlabs/console-services/conf.d/webserver.conf if there is no other viable way to check the cert.

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

Successfully merging this pull request may close these issues.

Check for console-cert expire date
2 participants