Searched refs:trust (Results 1 – 11 of 11) sorted by relevance
81 list of Mozilla trust purposes and levels for certificates to include in92 Valid trust levels are: **ALL**, **TRUSTED_DELEGATOR** (default), **NOT_TRUSTED**,125 The file format used by Mozilla for this trust information is documented here:127 https://p11-glue.freedesktop.org/doc/storing-trust-policy/storing-trust-existing.html
63 docker trust inspect --pretty "${DOCKER_IMAGE}"87 docker trust inspect --pretty "${DOCKER_IMAGE}"128 docker trust inspect --pretty "${DOCKER_IMAGE}"
1533 SecTrustRef trust = NULL; local1593 if(!trust) {1644 if(trust)1645 CFRelease(trust);1706 SecTrustRef trust; local1715 CFRelease(trust);2184 SecTrustRef trust = NULL; local2200 if(err == noErr && trust) {2208 CFRelease(trust);2230 CFRelease(trust);[all …]
42 i.e. that you can trust that the server is who the certificate says it is.43 This trust is based on a chain of digital signatures, rooted in certification69 certificate verification can make libcurl trust and use such information from
43 i.e. that you can trust that the server is who the certificate says it is.44 This trust is based on a chain of digital signatures, rooted in certification
48 i.e. that you can trust that the server is who the certificate says it is.49 This trust is based on a chain of digital signatures, rooted in certification
50 CURLOPT_UNRESTRICTED_AUTH(3) to 1L makes curl trust the server and sends
62 certificate verification can make libcurl trust and use such information from
25 This allows you to use a different trust for the proxy compared to the remote
40 --insecure can make curl trust and use such information from malicious
34 trust the gateway. This might be fine in local gateways that you host
Completed in 23 milliseconds
