2. Boost Beast Translation (zh_Hans)
3. Doc / Qbk / 03 Core / 9 Ssl Tls Certificate (qbk)
4. Chinese (Simplified Han script)
5. Zen

16 string ID 80
	Source string description type: paragraph
	English If used, the necessary CA certificates must be loaded into the server's SSL context to enable verification of the client's certificate.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — If used, the necessary CA certificates must be loaded into the server's SSL context to enable verification of the client's certificate. 135/1350 · 135 Needs editing (Needs rewriting)
17 string ID 85
	Source string description type: heading
	English Common Name and Subject Alternative Name
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Common Name and Subject Alternative Name 40/400 · 40 Needs editing (Needs rewriting)
18 string ID 87
	Source string description type: paragraph
	English The Subject Alternative Name (SAN) is an extension in X.509 certificates that allows multiple domain names, subdomains, or IP addresses to be associated with a single SSL/TLS certificate. Before that it was the Common Name field in the certificate subject which could contain a single hostname.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The Subject Alternative Name (SAN) is an extension in X.509 certificates that allows multiple domain names, subdomains, or IP addresses to be associated with a single SSL/TLS certificate. Before that it was the Common Name field in the certificate subject which could contain a single hostname. 294/2940 · 294 Needs editing (Needs rewriting)
19 string ID 93
	Source string description type: paragraph
	English recommends that if a certificate includes a SAN dNSName field, the client must ignore the subject CN field. Some modern browsers, such as Google Chrome, check only the SAN section in an SSL/TLS certificate and reject certificates that contain only the CN field.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — recommends that if a certificate includes a SAN dNSName field, the client must ignore the subject CN field. Some modern browsers, such as Google Chrome, check only the SAN section in an SSL/TLS certificate and reject certificates that contain only the CN field. 261/2610 · 261 Needs editing (Needs rewriting)
20 string ID 100
	Source string description type: heading
	English Private Key
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Private Key 11/110 · 11 Needs editing (Needs rewriting)
21 string ID 102
	Source string description type: paragraph
	English The private key of a certificate is required during the SSL/TLS handshake to prove that the certificate's provider is its rightful owner
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The private key of a certificate is required during the SSL/TLS handshake to prove that the certificate's provider is its rightful owner 136/1360 · 136 Needs editing (Needs rewriting)
22 string ID 105
	Source string description type: paragraph
	English The following Boost.Asio methods can be used for loading a private key:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The following Boost.Asio methods can be used for loading a private key: 71/710 · 71 Needs editing (Needs rewriting)
23 string ID 107
	Source string description type: list
	English * [@boost:/doc/html/boost_asio/reference/ssl__context/use_private_key.html `net::ssl::context::use_private_key`] * [@boost:/doc/html/boost_asio/reference/ssl__context/use_private_key_file.html `net::ssl::context::use_private_key_file`] * [@boost:/doc/html/boost_asio/reference/ssl__context/use_rsa_private_key.html `net::ssl::context::use_rsa_private_key`] * [@boost:/doc/html/boost_asio/reference/ssl__context/use_rsa_private_key_file.html `net::ssl::context::use_rsa_private_key_file`]
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — * [@boost:/doc/html/boost_asio/reference/ssl__context/use_private_key.html `net::ssl::context::use_private_key`] * [@boost:/doc/html/boost_asio/reference/ssl__context/use_private_key_file.html `net::ssl::context::use_private_key_file`] * [@boost:/doc/html/boost_asio/reference/ssl__context/use_rsa_private_key.html `net::ssl::context::use_rsa_private_key`] * [@boost:/doc/html/boost_asio/reference/ssl__context/use_rsa_private_key_file.html `net::ssl::context::use_rsa_private_key_file`] 487/4870 · 487 Needs editing (Needs rewriting)
24 string ID 112
	Source string description type: paragraph
	English If the private key is secured with a password, the [@boost:/doc/html/boost_asio/reference/ssl__context/set_password_callback.html net::ssl::context::set_password_callback] allows specifying a callable object to retrieve the password.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — If the private key is secured with a password, the [@boost:/doc/html/boost_asio/reference/ssl__context/set_password_callback.html net::ssl::context::set_password_callback] allows specifying a callable object to retrieve the password. 233/2330 · 233 Needs editing (Needs rewriting)
25 string ID 119
	Source string description type: heading
	English Self-Signed and Self-Issued Certificates
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Self-Signed and Self-Issued Certificates 40/400 · 40 Needs editing (Needs rewriting)
26 string ID 121
	Source string description type: paragraph
	English A self-issued certificate is a certificate where the issuer and subject are the same entity.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — A self-issued certificate is a certificate where the issuer and subject are the same entity. 92/920 · 92 Needs editing (Needs rewriting)
27 string ID 124
	Source string description type: paragraph
	English A self-signed certificate is a self-issued certificate in which the digital signature can be verified using the public key within the certificate.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — A self-signed certificate is a self-issued certificate in which the digital signature can be verified using the public key within the certificate. 146/1460 · 146 Needs editing (Needs rewriting)
28 string ID 128
	Source string description type: paragraph
	English Installing an untrusted, self-issued, or self-signed CA certificate poses a
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Installing an untrusted, self-issued, or self-signed CA certificate poses a 75/750 · 75 Needs editing (Needs rewriting)
29 string ID 137
	Source string description type: heading
	English Diffie-Hellman (DH) Parameters
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Diffie-Hellman (DH) Parameters 30/300 · 30 Needs editing (Needs rewriting)
30 string ID 139
	Source string description type: paragraph
	English Diffie-Hellman (DH) key exchange is a cryptographic protocol that allows two parties to securely establish a shared secret over an insecure communication channel. The key exchange process involves both parties agreeing on a set of parameters, known as Diffie-Hellman parameters, which include a large prime number `p` and a generator `g`. Since generating these parameters is a computationally expensive task, a user might prefer to provide a precomputed value at startup.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — Diffie-Hellman (DH) key exchange is a cryptographic protocol that allows two parties to securely establish a shared secret over an insecure communication channel. The key exchange process involves both parties agreeing on a set of parameters, known as Diffie-Hellman parameters, which include a large prime number `p` and a generator `g`. Since generating these parameters is a computationally expensive task, a user might prefer to provide a precomputed value at startup. 472/4720 · 472 Needs editing (Needs rewriting)
31 string ID 147
	Source string description type: paragraph
	English The following Boost.Asio methods can be used for loading DH parameters:
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — The following Boost.Asio methods can be used for loading DH parameters: 71/710 · 71 Needs editing (Needs rewriting)
32 string ID 149
	Source string description type: list
	English * [@boost:/doc/html/boost_asio/reference/ssl__context/use_tmp_dh.html `net::ssl::context::use_tmp_dh`] * [@boost:/doc/html/boost_asio/reference/ssl__context/use_tmp_dh_file.html `net::ssl::context::use_tmp_dh_file`]
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — * [@boost:/doc/html/boost_asio/reference/ssl__context/use_tmp_dh.html `net::ssl::context::use_tmp_dh`] * [@boost:/doc/html/boost_asio/reference/ssl__context/use_tmp_dh_file.html `net::ssl::context::use_tmp_dh_file`] 215/2150 · 215 Needs editing (Needs rewriting)
33 string ID 152
	Source string description type: paragraph
	English If no DH parameter is provided, OpenSSL will refuse to perform any handshake that uses DHE-based cipher suites but will still work with other cipher suites, such as those based on ECDHE.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — If no DH parameter is provided, OpenSSL will refuse to perform any handshake that uses DHE-based cipher suites but will still work with other cipher suites, such as those based on ECDHE. 186/1860 · 186 Needs editing (Needs rewriting)
34 string ID 158
	Source string description type: heading
	English A Self-Issued Certificate Example
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — A Self-Issued Certificate Example 33/330 · 33 Needs editing (Needs rewriting)
35 string ID 160
	Source string description type: paragraph
	English In the following example, we will generate a self-signed CA certificate and use it to issue both server and client certificates.
	Chinese (Simplified Han script) ↹ ↵ NBS … 「 」 『 』 ﹙-﹚ ‐ – — In the following example, we will generate a self-signed CA certificate and use it to issue both server and client certificates. 128/1280 · 128 Needs editing (Needs rewriting)