Describe the bug
First, thank you very much on your really helpful Splunk App!
I had an issue with the ssl_checker, not logging exiring certificates. In the first step I have found the config files need to be UTF-8 encoded. If the files had another encoding the python library codecs.py was raising an error.
I dont want to mix issues and would like to ask for your support regarding another issue. When I run the script on a Splunk deployment Server, the script is finding Certificates in the /etc/apps/deployment-apps directory.
Afterwards the script is checking the Certificate attributes. Here it is looking unter the path /opt/splunk/etc/apps/.../certname_appended.
It will not find the certificate there and quit with the error message:
"xxxx:error:xxxx:system library: fopen:No such file or directory......"
I have seen there was an option in ssl_checker Versions prior to 4.1.0.
I am not sure, if this is even the core issue. Because the Script still finds valid paths. But nothing is written in the defined index.
Is this the expected behavior or would it be possible to implement the "static" certs path option again?
Thank you very much and best regards.
To Reproduce
Steps to reproduce the behavior:
Run '/opt/splunk/etc/app/ssl_checker/bin/ssl_checker3.py' on a Deployment Server with Certificates in the /etc/deployment-apps/ directory.
See error fopen: No such file or directory.
Expected behavior
I was expecting the Certificates on the Deploymentserver in the path /etc/deployment-apps to be ignored
OR the certificated found unter /etc/deployment-apps to be checked in the system path they have been discovered.
Screenshots
If applicable, add screenshots to help explain your problem.
Name of the app ssl_checker https://splunkbase.splunk.com/app/3172
Describe the bug First, thank you very much on your really helpful Splunk App! I had an issue with the ssl_checker, not logging exiring certificates. In the first step I have found the config files need to be UTF-8 encoded. If the files had another encoding the python library codecs.py was raising an error.
I dont want to mix issues and would like to ask for your support regarding another issue. When I run the script on a Splunk deployment Server, the script is finding Certificates in the /etc/apps/deployment-apps directory. Afterwards the script is checking the Certificate attributes. Here it is looking unter the path /opt/splunk/etc/apps/.../certname_appended. It will not find the certificate there and quit with the error message: "xxxx:error:xxxx:system library: fopen:No such file or directory......"
I have seen there was an option in ssl_checker Versions prior to 4.1.0. I am not sure, if this is even the core issue. Because the Script still finds valid paths. But nothing is written in the defined index. Is this the expected behavior or would it be possible to implement the "static" certs path option again?
Thank you very much and best regards.
To Reproduce Steps to reproduce the behavior:
Expected behavior I was expecting the Certificates on the Deploymentserver in the path /etc/deployment-apps to be ignored OR the certificated found unter /etc/deployment-apps to be checked in the system path they have been discovered.
Screenshots If applicable, add screenshots to help explain your problem.