Lines Matching full:certificate
1 SSL Certificate Verification
23 This system is about trust. In your local CA certificate store you have certs
24 from *trusted* Certificate Authorities that you then can use to verify that the
34 Certificate Verification
37 libcurl performs peer SSL certificate verification by default. This is done
38 by using a CA certificate store that the SSL library can use to make sure the
39 peer's server certificate is valid.
45 If the remote server uses a self-signed certificate, if you don't install a CA
46 cert store, if the server uses a certificate signed by a CA that isn't
56 2. Get a CA certificate that can verify the remote server and use the proper
62 3. Add the CA cert for your server to the existing default CA certificate
63 store. The default CA certificate store can changed at compile time with the
66 --with-ca-bundle=FILE: use the specified file as CA certificate store. CA
69 --with-ca-path=PATH: use the specified path as CA certificate store. CA
82 - View the certificate by double-clicking the padlock
83 - Find out where the CA certificate is kept (Certificate>
89 - Add the 'outcert.pem' to the CA certificate store or use it stand-alone
97 - The certificate will have "BEGIN CERTIFICATE" and "END CERTIFICATE"
99 - If you want to see the data in the certificate, you can do: "openssl
102 - If you want to trust the certificate, you can add it to your CA
103 certificate store or use it stand-alone as described. Just remember that
104 the security is no better than the way you obtained the certificate.
125 certificate that isn't signed by one of the certificates in the installed CA
126 certificate store, will cause SSL to report an error ("certificate verify
130 Certificate Verification with NSS
137 p11-kit-nss-trust which makes NSS use the system wide CA certificate store. NSS
148 Certificate Verification with Schannel and Secure Transport
153 peer certificate verification, but instead of using a CA cert bundle, it will
