Searched refs:CA (Results 1 – 25 of 124) sorted by relevance
12345
38137 90001:Los Angeles, CA38138 90002:Los Angeles, CA38139 90003:Los Angeles, CA38140 90004:Los Angeles, CA38141 90005:Los Angeles, CA38142 90006:Los Angeles, CA38143 90007:Los Angeles, CA38144 90008:Los Angeles, CA38145 90009:Los Angeles, CA38146 90010:Los Angeles, CA[all …]
20 209:Lodi:California:CA21 209:Merced:California:CA22 209:Modesto:California:CA23 209:Stockton:California:CA27 213:Beverly Hills:California:CA28 213:Los Angeles:California:CA160 310:Compton:California:CA161 310:Santa Monica:California:CA162 310:Torrance:California:CA163 310:West LA:California:CA[all …]
6 CA.pl - friendlier interface for OpenSSL certificate programs10 B<CA.pl>27 The B<CA.pl> script is a perl script that supplies the relevant command line56 creates a new CA hierarchy for use with the B<ca> program (or the B<-signcert>57 and B<-xsign> options). The user is prompted to enter the filename of the CA59 details of the CA will be prompted for. The relevant files and directories64 create a PKCS#12 file containing the user certificate, private key and CA66 file "newcert.pem" and the CA certificate to be in the file demoCA/cacert.pem,84 file section B<v3_ca> and so makes the signed request a valid CA certificate. This85 is useful when creating intermediate CA from a root CA.[all …]
47 [B<-CA filename>]63 various forms, sign certificate requests like a "mini CA" or edit102 digest, such as the B<-fingerprint>, B<-signkey> and B<-CA> options. If not224 locally and must be a root CA: any certificate chain ending in this CA227 Trust settings currently are only used with a root CA. They allow a finer228 control over the purposes the root CA can be used for. For example a CA288 can thus behave like a "mini CA".312 the B<-signkey> or the B<-CA> options). Normally all extensions are338 the B<-signkey> or B<-CA> options. If used in conjunction with the B<-CA>345 =item B<-CA filename>[all …]
6 ca - sample minimal CA application50 The B<ca> command is a minimal CA application. It can be used57 =head1 CA OPTIONS73 signed by the CA.77 a single self signed certificate to be signed by the CA.82 and additional field values to be signed by the CA. See the B<SPKAC FORMAT>104 the CA certificate file.150 this option defines the CA "policy" to use. This is a section in152 or match the CA certificate. Check out the B<POLICY FORMAT> section318 the same as B<-cert>. It gives the file containing the CA[all …]
45 [B<-CA file>]137 file or pathname containing trusted CA certificates. These are used to verify152 root CA is not appropriate.184 do not use certificates in the response as additional untrusted CA225 If the B<index> option is present then the B<CA> and B<rsigner> options must also be228 =item B<-CA file>230 CA certificate corresponding to the revocation information in B<indexfile>.286 Otherwise the issuing CA certificate in the request is compared to the OCSP289 Otherwise the OCSP responder certificate's CA is checked against the issuing290 CA certificate in the request. If there is a match and the OCSPSigning[all …]
99 and ending in the root CA. It is an error if the whole chain cannot be built102 to be the root CA.116 is found the remaining lookups are from the trusted certificates. The root CA125 CA certificates. The precise extensions required are described in more detail in128 The third operation is to check the trust settings on the root CA. The root129 CA should be trusted for the supplied purpose. For compatibility with previous146 server.pem: /C=AU/ST=Queensland/O=CryptSoft Pty Ltd/CN=Test CA (1024 bit)147 error 24 at 1 depth lookup:invalid CA certificate153 then 1 for the CA that signed the certificate and so on. Finally a text version263 =item B<24 X509_V_ERR_INVALID_CA: invalid CA certificate>[all …]
5 SSL_CTX_load_verify_locations - set default locations for trusted CA18 which CA certificates for verification purposes are located. The certificates23 If B<CAfile> is not NULL, it points to a file of CA certificates in PEM24 format. The file can contain several CA certificates identified by27 ... (CA certificate in base64 encoding) ...36 If B<CApath> is not NULL, it points to a directory containing CA certificates37 in PEM format. The files each contain one CA certificate. The files are38 looked up by the CA subject name hash value, which must hence be available.39 If more than one CA certificate with the same name hash value exist, the49 When looking up CA certificates, the OpenSSL library will first search the[all …]
72 certificate), followed by intermediate CA certificates if applicable, and73 ending at the highest level (root) CA.126 complete certificate chains even when no trusted CA storage is used or127 when the CA issuing the certificate shall not be added to the trusted128 CA storage.131 TLS negotiation, CA certificates are additionally looked up in the132 locations of trusted CA certificates, see
23 the library will try to complete the chain from the available CA24 certificates in the trusted CA storage, see
24 it is not limited to CA certificates.28 Load names of CAs from file and use it as a client CA list:
67 the root CA certificate may be omitted according to the TLS standard and70 to leave out the root CA certificate). This can only be accomplished by71 either adding the intermediate CA certificates into the trusted73 CA certificates that otherwise maybe would not be trusted), or by adding
37 List of CA names explicitly set (for B<ctx> or in server mode) or send42 No client CA list was explicitly set (for B<ctx> or in server mode) or
27 SSL_CTX_add_client_CA() adds the CA name extracted from B<cacert> to the31 SSL_add_client_CA() adds the CA name extracted from B<cacert> to the55 CA list for B<ctx> or B<ssl> (as appropriate) is opened.
139 #define CA bfd_mach_i960_ca /*6*/ macro146 { ERROR, CORE, KA, KB, MC, XA, CA, JX, HX },147 { CORE, CORE, KA, KB, MC, XA, CA, JX, HX },152 { CA, CA, ERROR, ERROR, ERROR, ERROR, CA, ERROR, ERROR},
37 CA="$OPENSSL ca $SSLEAY_CONFIG"95 $CA -policy policy_anything -infiles newreq.pem 99 $CA -policy policy_anything -out newcert.pem -infiles newreq.pem107 $CA -policy policy_anything -out newcert.pem -infiles tmp.pem
45 certificate = $dir/cacert.pem # The CA certificate74 # For type CA, the listed attributes must be the same, and the optional78 # For the CA policy164 # requires this to avoid interpreting an end user certificate as a CA.166 basicConstraints=CA:FALSE214 basicConstraints = CA:FALSE220 # Extensions for a typical CA231 #basicConstraints = critical,CA:true233 basicConstraints = CA:true235 # Key usage: this is typical for a CA certificate. However since it will[all …]
21 my %CA;58 $CA{$p2}=$p3;82 print "sudoCommand: $_\n" foreach expand(\%CA,@cmds);
13 #CERTIssuer:/O=Root+20CA/OU=http://www.cacert.org/CN=CA+20Cert+20Signing+20Authority/emailAddress=s…
7 %C Berkeley, CA15 %C Berkeley, CA
10 # This section should be referenced when building an x509v3 CA16 basicConstraints=critical,CA:true,pathlen:$ENV::CERTPATHLEN
28 LATIN CAPITAL LETTER E WITH CIRCUMFLEX AND MACRON;00CA 030430 LATIN CAPITAL LETTER E WITH CIRCUMFLEX AND CARON;00CA 030C47 GURMUKHI PARI CA;0A4D 0A1A58 KHMER CONSONANT SIGN COENG CA;17D2 1785
123 if (__pfast == 0 && !CA)155 if (destline < outline && !(CA || UP))157 if (CA) {
1 …=AU/SP=Queensland/L=Brisbane/O=Cryptsoft Pty Ltd/OU=DEMONSTRATION AND TESTING/CN=DEMO ZERO VALUE CA10 …SP=Queensland, L=Brisbane, O=Cryptsoft Pty Ltd, OU=DEMONSTRATION AND TESTING, CN=DEMO ZERO VALUE CA