Identify non-valid (date/time) certificates #118
Description
Describe the problem
When looking for certificate candidates, several checks are made, e.g. for availability of key files and correct passwords, for "validity" (regarding date/time of valid from/to, i.e. expiration), and so on. From a logging point of view, it is not always easy to see why no valid certificate was found.
The evse_security interface does not expose a reason, but both the EvseSecurity module and libevse-security do some logging. Yet particularly identifying that the system clock is off, and therefore the properly deployed certificates fail to validate, is hard to see.
I would like to see some logging regarding this. I realize that potentially a bunch of found certificate files are checked, so logging the reason for each and every checked certificate may be too verbose. I am open for suggestions, or a hint whether more verbosity is okay.
Describe your solution
No response
Additional context
No response