You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: wolfSSL/src/chapter07.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,17 +10,17 @@ wolfSSL (formerly CyaSSL) has support for **PEM**, and **DER** formats for certi
10
10
11
11
**DER**, or “Distinguished Encoding Rules”, is a binary format of a certificate. DER file extensions can include `.der` and `.cer`, and cannot be viewed with a text editor.
12
12
13
-
An X.509 certificate is encoded using ASN.1 format. The DER format is the ASN.1 encoding. The PEM format is Base64 encoded and wrapped with a human readable header and footer. TLS send certificates in DER format.
13
+
An X.509 certificate is encoded using ASN.1 format. The DER format is the ASN.1 encoding. The PEM format is Base64 encoded and wrapped with a human readable header and footer. TLS sends certificates in DER format.
14
14
15
15
## Supported Certificate Extensions
16
16
17
17
18
18
If an unsupported or unknown extension that is marked as critical is found, then
19
19
an error message is returned, otherwise unsupported or unknown extensions found
20
-
are ignored. Certificate extension parsing expect that at the very least
20
+
are ignored. Certificate extension parsing expects that at the very least
21
21
`--enable-certext` (macro WOLFSSL_CERT_EXT) has been used when
22
22
compiling the wolfSSL library. This is a high level list of certificate
23
-
extensions that can be **parsed** and at least part if not all of the extensions
23
+
extensions that can be **parsed** and at least part, if not all, of the extensions
24
24
be used.
25
25
26
26
| Extension From [RFC 5280](https://datatracker.ietf.org/doc/html/rfc5280#section-4.2)| Supported |
@@ -405,7 +405,7 @@ Supported types are:
405
405
*`PKCS8_PRIVATEKEY_TYPE`
406
406
*`PKCS8_ENC_PRIVATEKEY_TYPE`
407
407
408
-
Now the buffer `pemCert<` holds the PEM format of the certificate.
408
+
Now the buffer `pemCert` holds the PEM format of the certificate.
409
409
410
410
If you wish to create a CA signed certificate then a couple of steps are required. After filling in the subject information as before, you’ll need to set the issuer information from the CA certificate. This can be done with `SetIssuer()` like this:
0 commit comments