Strange certificates validation behaviour on Windows (7) about windowsagent HOT 4 CLOSED

OK, you may close this issue.

The problem is twofold:

1. I had not added the (self-signed) certificate of the root certification authority (in my case C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert Assured ID Root CA)
2. (Guessed) Differences of implementation of libcurl on Windows/OpenSSL and Linux/GNUTLS

Because of the 2nd issue, issuing such a command on Windows fails (as it should do) if you don't provide the (self-signed) certificate of the root certification authority in the cacert.pem file:

curl -v --capath c:\temp --cacert "C:\ProgramData\OCS Inventory NG\Agent\cacert.pem" https://ocs-server.mycompany.be

while the corresponding command on linux works (though, it shouldn't in my opinion):

curl -v --capath /dev/null --cacert /var/lib/ocsinventory-agent/https\:__ocs-server.mycompany.be_ocsinventory/cacert.pem https://ocs-server.mycompany.be

Because, purportedly, in the later case, libcurl still uses the default /etc/ssl/certs folder and finds there the root CA certificate.

I'll rather open a bug against curl

from windowsagent.

Hi,

Our agents are using the libraires without any modifications ...
Maybe we need to upgrade our curl version to solve this problem ? ( atm the windows agent is using the 7.47 version )

Regards,
Gilles Dubois.

from windowsagent.

from windowsagent.

Hi @StCyr ,
curl librarie has been updated on last Windows Agent versions.

Regards,
Charlene Auger

from windowsagent.