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="nb-NO" datatype="plaintext" original="manual/encryption.md">

    <body>

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

        <source># 17 Encryption</source>

      </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">#### 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\_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.</target>

      </trans-unit>

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

        <source>#### Limitations