Zen

Translation

type: paragraph
The private key of a certificate is required during the SSL/TLS handshake to prove that the certificate's provider is its rightful owner
46/1360 · 136

Sign in to save translations.

English Chinese (Simplified Han script) Actions
It is important to set up peer verification so that the TLS/SSL handshake fails if certificate verification is unsuccessful:
设置对端验证非常重要，这样当证书验证失败时，TLS/SSL 握手也会随之失败：
A client must also verify that the hostname or IP address in the certificate matches the expected one. The [@boost:/doc/html/boost_asio/reference/ssl__host_name_verification.html `net::ssl::host_name_verification`] helper function object can perform this verification according to the rules described in RFC 6125:
客户端还需验证证书中的主机名或 IP 地址是否与预期一致。[@boost:/doc/html/boost_asio/reference/ssl__host_name_verification.html `net::ssl::host_name_verification`] 这个辅助函数对象，可以按照 RFC 6125 描述的规则来完成验证：
A server can also request and verify a client certificate to authenticate the client:
服务器也可以请求并验证客户端证书，以对客户端进行身份认证：
Server Certificate
服务器证书
A Server Certificate is a digital certificate that confirms a server's identity as the legitimate destination for a client. It contains a verifiable signature that ensures it was issued by a trusted certificate authority (CA).
服务器证书是一种数字证书，用于确认服务器身份是客户端的合法目的地。它包含可验证的签名，用于确保证书由受信任的证书授权机构（CA）签发。
When a server certificate is issued by an intermediate certificate authority, and the client lacks those intermediate certificates, the server should provide all the relevant certificates to the client. This allows the client to verify the final certificate in the chain against the root certificate.
当服务器证书由中间证书授权机构签发，且客户端缺少这些中间证书时，服务器应向客户端提供所有相关证书。这使得客户端能够根据根证书验证证书链中的最终证书。
The following Boost.Asio methods can be used for loading a certificate or a certificate chain:
以下 Boost.Asio 方法可用于加载单个证书或证书链：
* [@boost:/doc/html/boost_asio/reference/ssl__context/use_certificate.html `net::ssl::context::use_certificate`]
* [@boost:/doc/html/boost_asio/reference/ssl__context/use_certificate_file.html `net::ssl::context::use_certificate_file`]
* [@boost:/doc/html/boost_asio/reference/ssl__context/use_certificate_chain.html `net::ssl::context::use_certificate_chain`]
* [@boost:/doc/html/boost_asio/reference/ssl__context/use_certificate_chain_file.html `net::ssl::context::use_certificate_chain_file`]
* [@boost:/doc/html/boost_asio/reference/ssl__context/use_certificate.html `net::ssl::context::use_certificate`]
* [@boost:/doc/html/boost_asio/reference/ssl__context/use_certificate_file.html `net::ssl::context::use_certificate_file`]
* [@boost:/doc/html/boost_asio/reference/ssl__context/use_certificate_chain.html `net::ssl::context::use_certificate_chain`]
* [@boost:/doc/html/boost_asio/reference/ssl__context/use_certificate_chain_file.html `net::ssl::context::use_certificate_chain_file`]
Client Certificate
客户端证书
A server can authenticate clients by requiring and verifying their certificates, preventing access for those without a valid certificate and private key. The server enforces this by modifying peer verification settings:
服务器可以通过要求并验证客户端证书来对客户端进行身份认证，从而阻止没有有效证书和私钥的客户端访问。服务器通过修改对端验证设置来实施这一机制：
If used, the necessary CA certificates must be loaded into the server's SSL context to enable verification of the client's certificate.
若使用该机制，则需将必要的 CA 证书加载到服务器的 SSL 上下文中，以便能够验证客户端的证书。
Common Name and Subject Alternative Name
通用名称与主题备用名称
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.
主题备用名称（SAN）是 X.509 证书中的一种扩展字段，允许将多个域名、子域名或 IP 地址关联到同一张 SSL/TLS 证书上。在此之前，证书主题中的通用名称字段只能包含单个主机名。
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.
该建议指出，如果证书中包含 SAN 的 dNSName 字段，客户端必须忽略主题 CN 字段。某些现代浏览器（例如 Google Chrome）仅检查 SSL/TLS 证书中的 SAN 部分，并拒绝仅包含 CN 字段的证书。
Private Key
私钥
The private key of a certificate is required during the SSL/TLS handshake to prove that the certificate's provider is its rightful owner
证书的私钥在 SSL/TLS 握手过程中是必需的，用于证明证书的提供方是该证书的合法所有者。
The following Boost.Asio methods can be used for loading a private key:
以下 Boost.Asio 方法可用于加载私钥：
* [@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`]
* [@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`]
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.
如果私钥受密码保护，可以使用 [@boost:/doc/html/boost_asio/reference/ssl__context/set_password_callback.html net::ssl::context::set_password_callback] 设置一个可调用对象，用于获取该密码。
Self-Signed and Self-Issued Certificates
自签名证书与自颁发证书
A self-issued certificate is a certificate where the issuer and subject are the same entity.
自颁发证书是指证书的颁发者与主体为同一实体。
A self-signed certificate is a self-issued certificate in which the digital signature can be verified using the public key within the certificate.
自签名证书是一种自颁发证书，其数字签名可使用证书内的公钥进行验证。
Installing an untrusted, self-issued, or self-signed CA certificate poses a
安装不受信任、自颁发或自签名的 CA 证书会带来安全风险。
Diffie-Hellman (DH) Parameters
Diffie-Hellman（DH）参数
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.
Diffie-Hellman（DH）密钥交换是一种密码学协议，允许双方在不安全的通信通道上安全地建立共享密钥。该密钥交换过程涉及双方约定一组参数，即 Diffie-Hellman 参数，其中包括一个大素数 `p` 和一个生成元 `g`。由于生成这些参数是一项计算开销较大的任务，用户可能更倾向于在启动时提供预先计算好的值。
The following Boost.Asio methods can be used for loading DH parameters:
以下 Boost.Asio 方法可用于加载 DH 参数：
* [@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`]
* [@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`]
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.
如果未提供 DH 参数，OpenSSL 将拒绝执行任何使用基于 DHE 的加密套件的握手，但仍可与其他加密套件（例如基于 ECDHE 的套件）正常工作。
A Self-Issued Certificate Example
自颁发证书示例
In the following example, we will generate a self-signed CA certificate and use it to issue both server and client certificates.
在以下示例中，将生成一个自签名的 CA 证书，并使用该证书来签发服务器证书和客户端证书。
* Generate a CA certificate:
* 生成 CA 证书：
English Chinese (Simplified Han script) Actions
* Sign the Client CSR using our CA:
* 使用 CA 对客户端 CSR 进行签名：
A Server Certificate is a digital certificate that confirms a server's identity as the legitimate destination for a client. It contains a verifiable signature that ensures it was issued by a trusted certificate authority (CA).
服务器证书是一种数字证书，用于确认服务器身份是客户端的合法目的地。它包含可验证的签名，用于确保证书由受信任的证书授权机构（CA）签发。
Client Certificate
客户端证书
Common Name and Subject Alternative Name
通用名称与主题备用名称
A Certificate Authority (CA) is a trusted entity that signs digital certificates, enabling users to verify their authenticity. Rather than storing every individual certificate for each server (which would be impractical due to the sheer volume and frequent renewals), users can store a limited set of root certificates to authenticate server certificates as needed.
证书授权机构（CA）是一种可信实体，负责对数字证书进行签名，以便用户验证其真实性。由于服务器证书数量庞大且更新频繁，为每台服务器单独存储所有证书并不现实。因此，用户只需存储有限数量的根证书，即可在需要时验证服务器证书。
Server Certificate
服务器证书
The private key of a certificate is required during the SSL/TLS handshake to prove that the certificate's provider is its rightful owner
证书的私钥在 SSL/TLS 握手过程中是必需的，用于证明证书的提供方是该证书的合法所有者。
The following Boost.Asio methods can be used for loading a private key:
以下 Boost.Asio 方法可用于加载私钥：
* Sign the Server CSR using our CA:
* Sign the Server CSR using our CA:
It is important to set up peer verification so that the TLS/SSL handshake fails if certificate verification is unsuccessful:
设置对端验证非常重要，这样当证书验证失败时，TLS/SSL 握手也会随之失败：
The following Boost.Asio methods can be used for loading DH parameters:
以下 Boost.Asio 方法可用于加载 DH 参数：
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.
Diffie-Hellman（DH）密钥交换是一种密码学协议，允许双方在不安全的通信通道上安全地建立共享密钥。该密钥交换过程涉及双方约定一组参数，即 Diffie-Hellman 参数，其中包括一个大素数 `p` 和一个生成元 `g`。由于生成这些参数是一项计算开销较大的任务，用户可能更倾向于在启动时提供预先计算好的值。
A server can also request and verify a client certificate to authenticate the client:
服务器也可以请求并验证客户端证书，以对客户端进行身份认证：
Certificate Authority
证书授权机构
``` curl https://localhost:8080 --cacert ca.crt --cert client.crt --key client.key ```
``` curl https://localhost:8080 --cacert ca.crt --cert client.crt --key client.key ```
You can test the server using this cURL command:
可以使用以下 cURL 命令测试该服务器：
In the following example, we will generate a self-signed CA certificate and use it to issue both server and client certificates.
在以下示例中，将生成一个自签名的 CA 证书，并使用该证书来签发服务器证书和客户端证书。
``` openssl req -new -newkey rsa:4096 -keyout server.key -out server.csr -subj "/CN=localhost" -addext "subjectAltName=DNS:localhost,IP:127.0.0.1" ```
``` openssl req -new -newkey rsa:4096 -keyout server.key -out server.csr -subj "/CN=localhost" -addext "subjectAltName=DNS:localhost,IP:127.0.0.1" ```
A Self-Issued Certificate Example
自颁发证书示例
A self-signed certificate is a self-issued certificate in which the digital signature can be verified using the public key within the certificate.
自签名证书是一种自颁发证书，其数字签名可使用证书内的公钥进行验证。
SSL/TLS Certificate
SSL/TLS 证书

Loading…

User avatar Bstran

Translation changed
The private key of a certificate is required during the SSL/TLS handshake to prove that the certificate's provider is its rightful owner
The private key of a certificate is required during the SSL/TLS handshake to prove that the certificate's provider is its rightful owner证书的私钥在 SSL/TLS 握手过程中是必需的，用于证明证书的提供方是该证书的合法所有者。
06/13/2026
User avatar admin

String added in the repository
The private key of a certificate is required during the SSL/TLS handshake to prove that the certificate's provider is its rightful owner
The private key of a certificate is required during the SSL/TLS handshake to prove that the certificate's provider is its rightful owner
06/05/2026
Browse all string changes

Things to check

Mismatched full stop

Source and translation do not both end with a full stop.

Reset

Glossary

English Chinese (Simplified Han script)
No related strings found in the glossary.

String information

Source string description
type: paragraph
Unit identifier
59455
Source string location
string ID 102
String age
06/05/2026
Last updated
06/26/2026
Source string age
06/05/2026
Translation file QuickBook file
doc/qbk/03_core/9_ssl_tls_certificate_zh_Hans.qbk, string 21