-
Notifications
You must be signed in to change notification settings - Fork 96
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
Expiry warning breaks when insecure option is used #67
Comments
That is very interesting indeed. I have replicated at least partial issue against master:
|
Whats strange that other than its declaration the only place I see it used is here: https://github.com/sensu-plugins/sensu-plugins-http/blob/2.0.2/bin/check-http.rb#L248 |
I verified that this does not change depending on the option: https://github.com/sensu-plugins/sensu-plugins-http/blob/2.0.2/bin/check-http.rb#L251 |
Here is where its actually warning: https://github.com/sensu-plugins/sensu-plugins-http/blob/2.0.2/bin/check-http.rb#L297-L299 I validated that the presence or lack of |
I notice an unrelated bug: |
I can get it fail with self signed cert:
And it passing:
|
using the same thresholds both fail:
|
looks like one of the certs are set to expire and my guess would be an intermediate cert but I have not verified this. I will try to take a look tomorrow if I have some time. |
Looks like its comodos (in this case) that makes it fail with the full chain:
Where as the cert itself does not:
|
@cronnelly can you verify the same behavior running the equivalent commands against your env? |
@cronnelly you might consider using the |
I spoke with @eheydrick about this I don't see anyone "fixing" this unless you want to donate one. I will put together a pr to document this though as it's certainly a gotcha. |
The wrong expiry date is calculated when the
-k
(insecure) option is passed in. This then breaks expiry warning functionality.For example:
And then with
-k
:The text was updated successfully, but these errors were encountered: