Home
last modified time | relevance | path

Searched refs:PEM (Results 1 – 25 of 216) sorted by relevance

123456789

/third_party/mbedtls/tests/suites/
Dtest_suite_pem.data1 Standard PEM write
4 PEM write (zero data)
7 PEM write (one byte)
10 PEM write (more than line size)
13 PEM write (exactly two lines)
16 PEM write (exactly two lines + 1)
19 PEM read (unencrypted, valid)
22 PEM read (DES-EDE3-CBC + invalid iv)
26 PEM read (DES-CBC + invalid iv)
30 PEM read (unknown encryption algorithm)
[all …]
/third_party/libwebsockets/minimal-examples/crypto/minimal-crypto-x509/
DREADME.md5 - confirm one PEM cert or chain (-c) was signed by a trusted PEM cert (-t)
7 - convert a certificate public key and its private key PEM to a private JWK
24 -c <PEM certificate path>|Required PEM Certificate(s) to operate on... may be multiple concatednate…
25 -t <PEM certificate path>|Single PEM trusted certificate
26 -p <PEM private key path>|Optional private key matching certificate given in -c. If given, only th…
28 Example for confirming trust relationship. Notice the PEM in -c must contain not only
43 Example creating JWKs for public and public + private cert + PEM keys:
/third_party/mbedtls/tests/data_files/
DMakefile57 $(OPENSSL) x509 -inform PEM -in $< -outform DER -out $@
60 $(OPENSSL) pkey -in $< -out $@ -inform PEM -outform DER -passin "pass:$(test_ca_pwd_rsa)"
68 $(OPENSSL) x509 -in $< -out $@ -inform PEM -outform DER
76 $(OPENSSL) x509 -in $< -out $@ -inform PEM -outform DER
230 $(OPENSSL) x509 -in $(test_ca_crt_file_ec) -out $@ -inform PEM -outform DER
234 $(OPENSSL) pkey -in $(test_ca_key_file_ec) -out $@ -inform PEM -outform DER
304 $(OPENSSL) x509 -in $< -out $@ -inform PEM -outform DER
311 $(OPENSSL) pkey -in $< -out $@ -inform PEM -outform DER
390 $(OPENSSL) x509 -in $< -out $@ -inform PEM -outform DER
394 $(OPENSSL) pkey -in $< -out $@ -inform PEM -outform DER
[all …]
/third_party/openssl/doc/man7/
Dossl_store-file.pod28 In case a file is formatted as PEM, each called file handler receives
29 the PEM name (everything following any 'C<-----BEGIN >') as well as
30 possible PEM headers, together with the decoded PEM body. Since PEM
34 If the file isn't determined to be formatted as PEM, the content is
36 handlers as is, with no PEM name or headers.
38 Each file handler is expected to handle PEM and non-PEM content as
39 appropriate. Some may refuse non-PEM content for the sake of
43 OCTET STRING, so such keys would naturally be accepted as PEM files
/third_party/openssl/doc/man1/
Dopenssl-crl.pod.in12 [B<-inform> B<DER>|B<PEM>]
13 [B<-outform> B<DER>|B<PEM>]
15 [B<-keyform> B<DER>|B<PEM>|B<P12>]
37 This command processes CRL files in DER or PEM format.
47 =item B<-inform> B<DER>|B<PEM>
52 =item B<-outform> B<DER>|B<PEM>
54 The CRL output format; the default is B<PEM>.
61 =item B<-keyform> B<DER>|B<PEM>|B<P12>
142 Convert a CRL file from PEM to DER:
Dopenssl-crl2pkcs7.pod.in12 [B<-inform> B<DER>|B<PEM>]
13 [B<-outform> B<DER>|B<PEM>]
34 =item B<-inform> B<DER>|B<PEM>
36 The input format of the CRL; the default is B<PEM>.
39 =item B<-outform> B<DER>|B<PEM>
41 The output format of the PKCS#7 object; the default is B<PEM>.
56 Specifies a filename containing one or more certificates in B<PEM> format.
91 The B<PEM> encoded form with the header and footer lines removed can be used to
Dopenssl-pkcs7.pod.in16 [B<-inform> B<DER>|B<PEM>]
17 [B<-outform> B<DER>|B<PEM>]
40 =item B<-inform> B<DER>|B<PEM>, B<-outform> B<DER>|B<PEM>
42 The input and formats; the default is B<PEM>.
84 Convert a PKCS#7 file from PEM to DER:
Dopenssl-dsa.pod.in16 [B<-inform> B<DER>|B<PEM>]
17 [B<-outform> B<DER>|B<PEM>]
59 =item B<-inform> B<DER>|B<PEM>
64 =item B<-outform> B<DER>|B<PEM>
66 The key output format; the default is B<PEM>.
73 The B<PEM> format also accepts PKCS#8 data.
102 These options can only be used with PEM format output files.
161 To convert a private key from PEM to DER format:
Dopenssl-dsaparam.pod.in12 [B<-inform> B<DER>|B<PEM>]
13 [B<-outform> B<DER>|B<PEM>]
39 =item B<-inform> B<DER>|B<PEM>
44 =item B<-outform> B<DER>|B<PEM>
46 The DSA parameters output format; the default is B<PEM>.
Dopenssl-pkey.pod.in20 [B<-inform> B<DER>|B<PEM>|B<P12>|B<ENGINE>]
24 [B<-outform> B<DER>|B<PEM>]
77 =item B<-inform> B<DER>|B<PEM>|B<P12>|B<ENGINE>
108 =item B<-outform> B<DER>|B<PEM>
110 The key output format; the default is B<PEM>.
115 Encrypt the PEM encoded private key with the supplied cipher. Any algorithm
147 (possibly in addition to the PEM encoded form).
191 To convert a private key from PEM to DER format:
Dopenssl-rsa.pod.in16 [B<-inform> B<DER>|B<PEM>|B<P12>|B<ENGINE>]
17 [B<-outform> B<DER>|B<PEM>]
61 =item B<-inform> B<DER>|B<PEM>|B<P12>|B<ENGINE>
66 =item B<-outform> B<DER>|B<PEM>
68 The key output format; the default is B<PEM>.
103 These options can only be used with PEM format output files.
173 To convert a private key from PEM to DER format:
Dopenssl-dhparam.pod.in12 [B<-inform> B<DER>|B<PEM>]
13 [B<-outform> B<DER>|B<PEM>]
43 =item B<-inform> B<DER>|B<PEM>, B<-outform> B<DER>|B<PEM>
45 The input format and output format; the default is B<PEM>.
Dopenssl-ec.pod.in16 [B<-inform> B<DER>|B<PEM>|B<P12>|B<ENGINE>]
17 [B<-outform> B<DER>|B<PEM>]
52 =item B<-inform> B<DER>|B<PEM>|B<P12>|B<ENGINE>
57 =item B<-outform> B<DER>|B<PEM>
59 The key output format; the default is B<PEM>.
93 These options can only be used with PEM format output files.
164 To convert a private key from PEM to DER format:
Dopenssl-sess_id.pod.in12 [B<-inform> B<DER>|B<PEM>]
13 [B<-outform> B<DER>|B<PEM>|B<NSS>]
40 =item B<-inform> B<DER>|B<PEM>, B<-outform> B<DER>|B<PEM>|B<NSS>
42 The input and output formats; the default is PEM.
/third_party/curl/docs/cmdline-opts/
Dcert-type.md7 Help: Certificate type (DER/PEM/ENG/P12)
16 - --cert-type PEM --cert file $URL
21 Tells curl what type the provided client certificate is using. PEM, DER, ENG
24 The default type depends on the TLS backend and is usually PEM, however for
Dkey-type.md6 Help: Private key file type (DER/PEM/ENG)
20 is. DER, PEM, and ENG are supported. If not specified, PEM is assumed.
/third_party/openssl/doc/man3/
DPEM_bytes_read_bio.pod5 PEM_bytes_read_bio, PEM_bytes_read_bio_secmem - read a PEM-encoded data structure from a BIO
20 PEM_bytes_read_bio() reads PEM-formatted (IETF RFC 1421 and IETF RFC 7468)
23 etc.). If multiple PEM-encoded data structures are present in the same
25 continue reading. Non-PEM data present in the stream may cause an
28 The PEM header may indicate that the following data is encrypted; if so,
50 storage allocated within the PEM processing stack. The BIO stack from
53 that the contents of the PEM file only appears in memory from the secure heap,
DPEM_read.pod7 - PEM encoding routines
29 These functions read and write PEM-encoded objects, using the PEM
33 PEM is the term used for binary content encoding first defined in IETF
56 Both skip any non-PEM data that precedes the start of the next PEM object.
93 includes the case when no more PEM objects remain in the input file.
96 PEM objects were found. See L<ERR_peek_last_error(3)>, L<ERR_GET_REASON(3)>.
105 This is because the underlying PEM encryption format is obsolete, and should
DPEM_read_bio_PrivateKey.pod34 PEM_write_bio_PKCS7, PEM_write_PKCS7 - PEM routines
199 The PEM functions read or write structures in PEM format. In
200 this sense PEM format is simply base64 encoded data surrounded
204 B<PEM FUNCTION ARGUMENTS> section.
219 to the relevant PEM function. See the L</EXAMPLES> section below.
221 The B<PrivateKey> functions read or write a private key in PEM format using
233 specifies the encryption algorithm to use: unlike some other PEM routines the
234 encryption is applied at the PKCS#8 level and not in the PEM headers. If
272 The B<Parameters> functions read or write key parameters in PEM format using
306 =head1 PEM FUNCTION ARGUMENTS
[all …]
/third_party/libcoap/
DHOWTO.pkcs1123 # Assumption is that you already have the following PEM files
25 # server-cert.pem - Contains the server certificate in PEM format
26 # server-key.pem - Contains the server private key in PEM format
27 # client-cert.pem - Contains the server certificate in PEM format
28 # client-key.pem - Contains the server private key in PEM format
59 openssl pkcs8 -topk8 -inform PEM -outform PEM -in server-key.pem \
72 openssl pkcs8 -topk8 -inform PEM -outform PEM -in client-key.pem \
/third_party/curl/docs/libcurl/opts/
DCURLOPT_SSLCERTTYPE.md29 Supported formats are "PEM" and "DER", except with Secure Transport or
39 "PEM"
55 curl_easy_setopt(curl, CURLOPT_SSLCERTTYPE, "PEM");
DCURLOPT_PROXY_SSLCERTTYPE.md30 Supported formats are "PEM" and "DER", except with Secure Transport or
40 "PEM"
57 curl_easy_setopt(curl, CURLOPT_PROXY_SSLCERTTYPE, "PEM");
DCURLOPT_SSLKEYTYPE.md28 the format of your private key. Supported formats are "PEM", "DER" and "ENG".
40 "PEM"
57 curl_easy_setopt(curl, CURLOPT_SSLKEYTYPE, "PEM");
DCURLOPT_CAINFO_BLOB.md16 CURLOPT_CAINFO_BLOB - Certificate Authority (CA) bundle in PEM format
30 and size) about a memory block with binary data of PEM encoded content holding
57 char *strpem; /* strpem must point to a PEM string */
DCURLOPT_SSLKEY_BLOB.md28 and size) for a private key. Compatible with OpenSSL. The format (like "PEM")
67 curl_easy_setopt(curl, CURLOPT_SSLCERTTYPE, "PEM");
73 curl_easy_setopt(curl, CURLOPT_SSLKEYTYPE, "PEM");

123456789