mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 07:37:19 -04:00
255c9a7f95
**Problem:** For historical reasons, source files for the Elasticsearch Guide's security, watcher, and Logstash API docs are housed in the `x-pack/docs` directory. This can confuse new contributors who expect Elasticsearch Guide docs to be located in `docs/reference`. **Solution:** - Move the security, watcher, and Logstash API doc source files to the `docs/reference` directory - Update doc snippet tests to use security Rel: https://github.com/elastic/platform-docs-team/issues/208
25 lines
1.3 KiB
Text
25 lines
1.3 KiB
Text
[role="xpack"]
|
|
[[ciphers]]
|
|
=== Enabling cipher suites for stronger encryption
|
|
|
|
The TLS and SSL protocols use a cipher suite that determines the strength of
|
|
encryption used to protect the data. You may want to increase the strength of
|
|
encryption used when using a Oracle JVM; the IcedTea OpenJDK ships without these
|
|
restrictions in place. This step is not required to successfully use encrypted
|
|
communication.
|
|
|
|
The _Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy
|
|
Files_ enable the use of additional cipher suites for Java in a separate JAR file
|
|
that you need to add to your Java installation. You can download this JAR file
|
|
from Oracle's http://www.oracle.com/technetwork/java/javase/downloads/index.html[download page].
|
|
The _JCE Unlimited Strength Jurisdiction Policy Files`_ are required for
|
|
encryption with key lengths greater than 128 bits, such as 256-bit AES encryption.
|
|
|
|
After installation, all cipher suites in the JCE are available for use but requires
|
|
configuration in order to use them. To enable the use of stronger cipher suites
|
|
with {es} {security-features}, configure the
|
|
<<ssl-tls-settings,`cipher_suites` parameter>>.
|
|
|
|
NOTE: The _JCE Unlimited Strength Jurisdiction Policy Files_ must be installed
|
|
on all nodes in the cluster to establish an improved level of encryption
|
|
strength.
|