CAs (reference) in projects: third_party

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched refs:CAs (Results 1 – 25 of 60) sorted by relevance

12 3

/third_party/openssl/doc/man3/
D	SSL_CTX_set0_CA_list.pod	65 SSL_CTX_set_client_CA_list() sets the B<list> of CAs sent to the client when 69 SSL_set_client_CA_list() sets the B<list> of CAs sent to the client when 74 SSL_CTX_get_client_CA_list() returns the list of client CAs explicitly set for 78 SSL_get_client_CA_list() returns the list of client CAs explicitly 81 SSL_get_client_CA_list returns the list of client CAs sent from the server, if 85 list of CAs sent to the client when requesting a client certificate for 89 list of CAs sent to the client when requesting a client certificate for 106 SSL_CTX_set0_CA_list() sets the list of CAs to be sent to the peer to 110 SSL_set0_CA_list() sets the list of CAs to be sent to the peer to B<name_list> 114 SSL_CTX_get0_CA_list() retrieves any previously set list of CAs set for [all …]
D	SSL_CTX_free.pod	`19 applicable: the session cache, the list of ciphers, the list of Client CAs,`
D	CMS_sign_receipt.pod	`21 in the CMS structure (for example any intermediate CAs in the chain).`
D	SSL_load_client_CA_file.pod	`59 Load names of CAs from file and use it as a client CA list:`
D	PKCS7_verify.pod	`52 are used as untrusted CAs. If any chain verify fails an error code is returned. 74 not used as untrusted CAs. This means that the whole verify chain (apart from`
D	SSL_CTX_add1_chain_cert.pod	`59 existing chain certificates as untrusted CAs, B<SSL_BUILD_CHAIN_FLAG_NO_ROOT> 111 subordinate CAs are sent in the correct order. Misconfigured applications`
D	X509_STORE_add_cert.pod	`56 trusted entities such as root certificate authorities (CAs).`
D	SSL_CTX_set_client_cert_cb.pod	`50 certificate is sent, if it matches the list of acceptable CAs sent by the`
D	X509_LOOKUP_hash_dir.pod	`72 set of CAs.`
/third_party/node/test/parallel/
D	test-tls-server-verify.js	`51 CAs: ['ca1-cert'], property 63 CAs: ['ca1-cert'], property 75 CAs: ['ca1-cert'], property 87 CAs: ['ca1-cert'], property 99 CAs: ['ca1-cert', 'ca2-cert'], property 112 CAs: ['ca2-cert'], property 249 const cas = tcase.CAs.map(loadPEM);`
/third_party/libcoap/man/
D	coap-rd.txt.in	`86 PEM file that contains a list of one or more CAs that are to 88 to use. Normally, this list of CAs would be the root CA and and any 89 intermediate CAs. Ideally the server certificate should be signed by the 91 cafile are added to the trusted store of root CAs. Using the -C or -R 96 PEM file containing the set of trusted root CAs that are to be used to`
D	coap-server.txt.in	`164 PEM file or PKCS11 URI that contains a list of one or more CAs that are to 166 to use. Normally, this list of CAs would be the root CA and and any 167 intermediate CAs. Ideally the server certificate should be signed by the 169 cafile are added to the trusted store of root CAs. Using the -C or -R 182 PEM file containing the set of trusted root CAs that are to be used to`
D	coap_endpoint_server.txt.in	`85 coap_context_set_pki_root_cas() - if the root CAs need to be updated and PKI 100 root CAs to be used instead of the default set of root CAs provided as a part 102 list of CAs. _ca_file can be NULL. _ca_dir_ points to a directory 105 NOTE: Some TLS libraries send the full list of CAs added by this function`
D	coap_encryption.txt.in	86 coap_context_set_pki_root_cas() - if the root CAs need to be updated and PKI 99 coap_context_set_pki_root_cas() - if the root CAs need to be updated and PKI 407 in to the list of valid CAs for Certificate checking. 501 list of valid CAs are sent to client. For the client, the logic will check 517 is the number of intermediate CAs in the chain. If set to 0, then there can be 698 the valid root CAs list if not already present. 725 the valid root CAs list if not already present. 781 the valid root CAs list if not already present. 818 is also added into the valid root CAs list if not already present.
D	coap-client.txt.in	`208 to the trusted store of root CAs. Using the -C or -R options will trigger 220 PEM file containing the set of trusted root CAs that are to be used to`
/third_party/mbedtls/tests/data_files/
D	Readme-x509.txt	`1 This documents the X.509 CAs, certificates, and CRLS used for testing. 6 There are two main CAs for use as trusted roots: 16 Two intermediate CAs are signed by them: 27 Finally, other CAs for specific purposes:`
/third_party/libwebsockets/minimal-examples/http-client/minimal-http-client-jit-trust/
D	README.md	`3 This example turns off any existing trusted CAs and then tries to connect to a server, by default, … 5 It validates the remote certificates using trusted CAs from a JIT Trust blob compiled into the code.`
/third_party/openssl/doc/man1/
D	crl2pkcs7.pod	`86 This utility can be used to send certificates and CAs to Netscape as part of 91 install user certificates and CAs in MSIE using the Xenroll control.`
D	pkcs7.pod	`95 For compatibility with some CAs it will also accept:`
/third_party/curl/docs/
D	SSLCERTS.md	`25 server certificates you see are valid. They're signed by one of the CAs you 28 Which CAs do you trust? You can decide to trust the same set of companies your 32 companies and recent years several such CAs have been found untrustworthy. 42 certificates that are signed by CAs present in the store, you can be sure`
/third_party/libwebsockets/READMEs/
D	README.jit-trust.md	`28 but you don't have heap spare to preload all the CAs, you need something like 95 three cases where they have removed or distrusted CAs from it by their own 176 might meet certificates that trust multiple valid CAs that can validate the 186 matched CAs, if there is no existing JIT vhost with its tls context configured 187 with the needed trusted CAs, one is created. 202 and add an entry in the cache for this hostname to the SKIDs of the CAs`
/third_party/libwebsockets/minimal-examples/crypto/minimal-crypto-x509/
D	README.md	`29 the final certificate but also the certificates for any intermediate CAs.`
/third_party/openssl/apps/
D	openssl.cnf	`169 # This goes against PKIX guidelines but some CAs do it and some software 270 # This goes against PKIX guidelines but some CAs do it and some software`
D	openssl-vms.cnf	`169 # This goes against PKIX guidelines but some CAs do it and some software 270 # This goes against PKIX guidelines but some CAs do it and some software`
/third_party/node/doc/api/
D	tls.md	814 determine if the server certificate was signed by one of the specified CAs. If 888 Returns `true` if the peer certificate was signed by one of the CAs specified 1289 verified against the list of supplied CAs. An `'error'` event is emitted if 1434 verified against the list of supplied CAs. An `'error'` event is emitted if 1621 certificates. Default is to trust the well-known CAs curated by Mozilla. 1622 Mozilla's CAs are completely replaced when CAs are explicitly specified 1625 CAs concatenated together. The peer's certificate must be chainable to a CA 1631 default CAs, use the `ca` option to provide a CA certificate that the peer's 1750 [Mozilla's publicly trusted list of CAs][]. 1855 connection which is not authorized with the list of supplied CAs. This [all …]

12 3