ca

I have a certificate chain in server: Certificate chain 0 s:/******/O=Foobar International BV/OU**** i:/C=US/O=Symantec Corporation/OU=Symantec Trust Network/**** 1 s:/C=US/O=Symantec Corporation/OU=Symantec Trust Network/**** i:/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=**** - G5 2 s:/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=**** - G5 i:/C=US/O=VeriSign, Inc./OU=Class 3 Public Primary Certification Authority And my local root CA certificate is: s:/C=US/O=Symantec Corporation/OU=Symantec Trust Network/**** i:/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=**** - G5 And I

I am trying to add certificate Authority (CA) file name - ca.crt to /etc/ssl/certs , for that I followed this article . I copied my ca.crt file to /etc/pki/ca-trust/source/anchors/ and run the command below; update-ca-trust extract After that I checked /etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt file, but I didn't find my CA. I am not able to figure out what may be the problem. What am I doing wrong and how can I fix it? copy your certificates inside /etc/pki/ca-trust/source/anchors/ then run the following command update-ca-trust find *.pem file and place it to the anchors sub

I have an android application that is connecting to an SSL web service that we host. The Web server is apache and has its own CA that we created and a self signed SSL certificate. I have imported our CA certificate onto the Android tablet in the User Trusted certificates section in Security. I have tested access to the web server and can confirm that the web service certificate shows as valid (screenshot below) Here is the certificate in the security settings: Now when I try and access the webservice in my application I get the "No Peer Certificate" exception being triggered. This is the SSL

I am looking for a way to add a custom CA to NPM so I can download from a location using said certificate (an internal git-server) without having to nuke all CA-checking with npm config set strict-ssl false Is there any way of achieving this or not? (if not: is there already a defect?) You can point npm to a cafile npm config set cafile /path/to/cert.pem You can also configure ca string(s) directly. npm config set ca "cert string" ca can be an array of cert strings too. In your .npmrc : ca[]="cert 1 base64 string" ca[]="cert 2 base64 string" The npm config commands above will persist the

Although, there are similar questions , and even good answers , they either don't concern themselves with localhost specifically, or ask about one particular option/solution (self-signed vs CA). What are the options? How do they compare? Ho do I do this? tl;dr Generate a certificate issued by own CA (see the script below) Here's what I've found. Correct me where I'm wrong. There are CA's (certificate authorities). They issue certificates (sign CSR's) for other CA's (intermediate CA's), or servers (end entity certificates). Some of them are root authorities. They have self-signed certificates,