Source of encryption.xliff - documentation

|*OpenSSL 1.1.1d*|TLS\_AES\_256\_GCM\_SHA384&lt;br&gt;TLS\_CHACHA20\_POLY1305\_SHA256&lt;br&gt;TLS\_AES\_128\_GCM\_SHA256&lt;br&gt;ECDHE-RSA-AES128-GCM-SHA256&lt;br&gt;ECDHE-RSA-AES128-SHA256&lt;br&gt;ECDHE-RSA-AES128-SHA&lt;br&gt;AES128-GCM-SHA256&lt;br&gt;AES128-CCM8&lt;br&gt;AES128-CCM&lt;br&gt;AES128-SHA256&lt;br&gt;AES128-SHA|TLS\_CHACHA20\_POLY1305\_SHA256&lt;br&gt;TLS\_AES\_128\_GCM\_SHA256&lt;br&gt;ECDHE-PSK-AES128-CBC-SHA256&lt;br&gt;ECDHE-PSK-AES128-CBC-SHA&lt;br&gt;PSK-AES128-GCM-SHA256&lt;br&gt;PSK-AES128-CCM8&lt;br&gt;PSK-AES128-CCM&lt;br&gt;PSK-AES128-CBC-SHA256&lt;br&gt;PSK-AES128-CBC-SHA|</source>

<?xml version='1.0' encoding='UTF-8'?>

<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">

  <file source-language="en" target-language="zh-CN" datatype="plaintext" original="manual/encryption.md">

    <body>

      <trans-unit id="822969ff" xml:space="preserve">

        <source># 17 Encryption</source>

        <target># 17. 加密</target>

      </trans-unit>

      <trans-unit id="0b118c23" xml:space="preserve">

        <source>#### Overview

Zabbix supports encrypted communications between Zabbix components using

Transport Layer Security (TLS) protocol v.1.2 and 1.3 (depending on the

crypto library). Certificate-based and pre-shared key-based encryption

is supported.

Encryption can be configured for connections:

-   Between Zabbix server, Zabbix proxy, Zabbix agent, Zabbix web service, zabbix\_sender

    and zabbix\_get utilities

-   To Zabbix database [from Zabbix frontend and

    server/proxy](/manual/appendix/install/db_encrypt)

Encryption is optional and configurable for individual components:

-   Some proxies and agents can be configured to use certificate-based

    encryption with the server, while others can use pre-shared

    key-based encryption, and yet others continue with unencrypted

    communications (as before)

-   Server (proxy) can use different encryption configurations for

    different hosts

Zabbix daemon programs use one listening port for encrypted and

unencrypted incoming connections. Adding an encryption does not require

opening new ports on firewalls.</source>

        <target state="needs-translation">

#### 概述

Zabbix支持使用TLS协议v.1.2和1.3(取决于加密库)在Zabbix组件之间进行加密通信。支持证书加密和预共享密钥加密。

可以为连接配置加密:

-   Zabbix server，Zabbix proxy，Zabbix agent，Zabbix \_sender和Zabbix \_get工具

-   到Zabbix数据库[从zabbix前端和server/proxy](/manual/appendix/install/db_encrypt)

加密是可选和可配置的单个组件:

-   一些proxy和agent可以配置为使用服务器的基于证书的加密，而其他的可以使用基于预共享密钥的加密，而其他的则继续使用未加密的通信(与前面一样)

-   Server (proxy) 可以为不同的主机使用不同的加密配置。

Zabbix守护程序为传入的加密和非加密连接使用一个侦听端口。 添加加密并不需要在防火墙上打开新的端口。</target>

      </trans-unit>

      <trans-unit id="bdc6b202" xml:space="preserve">

        <source>#### Limitations

-   Private keys are stored in plain text in files readable by Zabbix

    components during startup

-   Pre-shared keys are entered in Zabbix frontend and stored in Zabbix

    database in plain text

-   Built-in encryption does not protect communications:

    -   Between the web server running Zabbix frontend and user web

        browser