You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicecomb.apache.org by li...@apache.org on 2020/04/08 00:33:29 UTC

[servicecomb-docs] 02/02: fix default value error

This is an automated email from the ASF dual-hosted git repository.

liubao pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-docs.git

commit 6c24f62809eb3d3b4daab25f47b1963e48f0f5d3
Author: liubao <bi...@qq.com>
AuthorDate: Tue Apr 7 19:58:04 2020 +0800

    fix default value error
---
 java-chassis-reference/en_US/docs/security/tls.md | 4 ++--
 java-chassis-reference/zh_CN/docs/security/tls.md | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/java-chassis-reference/en_US/docs/security/tls.md b/java-chassis-reference/en_US/docs/security/tls.md
index adf91e8..8b0354d 100644
--- a/java-chassis-reference/en_US/docs/security/tls.md
+++ b/java-chassis-reference/en_US/docs/security/tls.md
@@ -59,8 +59,8 @@ The certificate configuration items are shown in Table 1. Certificate Configurat
 | Ssl.engine| jdk | - | No | ssl protocol, provide jdk/openssl options | default jdk |
 | ssl.protocols | TLSv1.2 | - | No | Protocol List | separated by comma |
 | ssl.ciphers | TLS\_ECDHE\_RSA\_WITH\_AES\_256\_GCM\_SHA384,<br/>TLS\_ECDHE\_RSA\_WITH \_AES\_128\_GCM\_SHA256 | - | No| List of laws | separated by comma |
-| ssl.authPeer | true | - | No | Whether to authenticate the peer | - |
-| ssl.checkCN.host | true | - | No | Check whether the CN of the certificate is checked. | This configuration item is valid only on the Consumer side and is valid using the http protocol. That is, the Consusser side uses the rest channel. Invalid for Provider, highway, etc. The purpose of checking CN is to prevent the server from being phishing, refer to Standard definition: [https://tools.ietf.org/html/rfc2818. ](https://tools.ietf.org/html/rfc2818.) |
+| ssl.authPeer | false | - | No | Whether to authenticate the peer | - |
+| ssl.checkCN.host | false | - | No | Check whether the CN of the certificate is checked. | This configuration item is valid only on the Consumer side and is valid using the http protocol. That is, the Consusser side uses the rest channel. Invalid for Provider, highway, etc. The purpose of checking CN is to prevent the server from being phishing, refer to Standard definition: [https://tools.ietf.org/html/rfc2818. ](https://tools.ietf.org/html/rfc2818.) |
 | ssl.trustStore | trust.jks | - | No | Trust certificate file | - |
 | ssl.trustStoreType | JKS | - | No | Trust Certificate Type | - |
 | ssl.trustStoreValue | - | - | No | Trust Certificate Password | - |
diff --git a/java-chassis-reference/zh_CN/docs/security/tls.md b/java-chassis-reference/zh_CN/docs/security/tls.md
index d9b4e51..cb098da 100644
--- a/java-chassis-reference/zh_CN/docs/security/tls.md
+++ b/java-chassis-reference/zh_CN/docs/security/tls.md
@@ -57,8 +57,8 @@ ssl.[tag].[property]
 | ssl.engine| jdk | - | 否 | ssl协议,提供jdk/openssl选择 | 默认为jdk |
 | ssl.protocols | TLSv1.2 | - | 否 | 协议列表 | 使用逗号分隔 |
 | ssl.ciphers | TLS\_ECDHE\_RSA\_WITH\_AES\_256\_GCM\_SHA384,<br/>TLS\_ECDHE\_RSA\_WITH\_AES\_128\_GCM\_SHA256 | - | 否 | 算法列表 | 使用逗号分隔 |
-| ssl.authPeer | true | - | 否 | 是否认证对端 | - |
-| ssl.checkCN.host | true | - | 否 | 是否对证书的CN进行检查 | 该配置项只对Consumer端,并且使用http协议有效,即Consumser端使用rest通道有效。对于Provider端、highway通道等无效。检查CN的目的是防止服务器被钓鱼,参考标准定义:[https://tools.ietf.org/html/rfc2818。](https://tools.ietf.org/html/rfc2818。) |
+| ssl.authPeer | false | - | 否 | 是否认证对端 | - |
+| ssl.checkCN.host | false | - | 否 | 是否对证书的CN进行检查 | 该配置项只对Consumer端,并且使用http协议有效,即Consumser端使用rest通道有效。对于Provider端、highway通道等无效。检查CN的目的是防止服务器被钓鱼,参考标准定义:[https://tools.ietf.org/html/rfc2818。](https://tools.ietf.org/html/rfc2818。) |
 | ssl.trustStore | trust.jks | - | 否 | 信任证书文件 | - |
 | ssl.trustStoreType | JKS | - | 否 | 信任证书类型 | - |
 | ssl.trustStoreValue | - | - | 否 | 信任证书密码 | - |