From 4a091dacb88197288501d7f671183b46a94db711 Mon Sep 17 00:00:00 2001 From: genie-openj9 Date: Fri, 29 Sep 2023 12:03:39 +0000 Subject: [PATCH] Generated from commit: 0fe45ea64e1c0d66ea8ed690c8b0402674570ec6 Signed-off-by: genie-openj9 --- builds/index.html | 2 +- jitserver/index.html | 2 +- openssl/index.html | 6 +- search/search_index.json | 2 +- sitemap.xml | 618 +++++++++++++++++----------------- sitemap.xml.gz | Bin 2497 -> 2497 bytes version0.41/index.html | 17 + xxjitserversslcert/index.html | 2 +- 8 files changed, 333 insertions(+), 316 deletions(-) diff --git a/builds/index.html b/builds/index.html index e0cc6e935e..f788895ad8 100644 --- a/builds/index.html +++ b/builds/index.html @@ -8081,7 +8081,7 @@

Building your own binaries

Installation pre-requisites

Note the following:

diff --git a/jitserver/index.html b/jitserver/index.html index a5942d666e..2ccfb80884 100644 --- a/jitserver/index.html +++ b/jitserver/index.html @@ -8198,7 +8198,7 @@

Configuring JITServer technology

If a JITServer server crashes, the client is forced to perform compilations locally. You can change this behavior by using the -XX:[+|-]RequireJITServer option so that the client crashes with an assert when it detects that the server is unavailable. This feature is useful when you are running a test suite with JITServer enabled and you want the server crash to cause the test to fail.

Security

-

You can encrypt network communication between the client VM and JITServer by using OpenSSL 1.0.x, 1.1.x, or 3.0.x. To enable encryption, you specify the private key and the certificate at the server and use the certificate at the client. For more information, see -XX:JITServerSSLCert / -XX:JITServerSSLKey / -XX:JITServerSSLRootCerts.

+

You can encrypt network communication between the client VM and JITServer by using OpenSSL 1.0.x, 1.1.x, or 3.x. To enable encryption, you specify the private key and the certificate at the server and use the certificate at the client. For more information, see -XX:JITServerSSLCert / -XX:JITServerSSLKey / -XX:JITServerSSLRootCerts.

Tuning JITServer

For best practices regarding JITServer configuration and tuning, see the document JITServer tuning and practical considerations.

Building a JDK with JITServer technology

diff --git a/openssl/index.html b/openssl/index.html index 6df897d53b..ad80234431 100644 --- a/openssl/index.html +++ b/openssl/index.html @@ -7992,10 +7992,10 @@ -->

OpenSSL

-

OpenJDK uses the in-built Java™ cryptographic implementation by default but Eclipse OpenJ9™ also provides some support for the OpenSSL cryptographic library. OpenSSL is an open source cryptographic toolkit for Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols, which is well established and used with many enterprise applications. Because it is a native library, OpenSSL might provide better performance. To use OpenSSL cryptographic acceleration, install OpenSSL 1.0.x, 1.1.x, or 3.0.x (Linux® only) on your system. The OpenSSL V1.0.x, V1.1.x, and V3.0.x implementations are currently supported for the Digest, CBC, GCM, RSA, ECDH key agreement, and EC key generation algorithms. The OpenSSL V1.1.x and V3.0.x implementations are also supported for the ChaCha20 and ChaCha20-Poly1305 algorithms. The OpenSSL V1.1.1 onwards implementations are supported for the XDH key agreement and XDH key generation algorithms.

-

On Linux and AIX® operating systems, the OpenSSL 1.0.x or 1.1.x library is expected to be found on the system path. If you use a package manager to install OpenSSL, the system path will be updated automatically. On other operating systems, the OpenSSL 1.1.x library is typically bundled. Later levels of some Linux operating systems might bundle OpenSSL 3.0.x.

+

OpenJDK uses the in-built Java™ cryptographic implementation by default but Eclipse OpenJ9™ also provides some support for the OpenSSL cryptographic library. OpenSSL is an open source cryptographic toolkit for Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols, which is well established and used with many enterprise applications. Because it is a native library, OpenSSL might provide better performance. To use OpenSSL cryptographic acceleration, install OpenSSL 1.0.x, 1.1.x, or 3.x on your system. The OpenSSL V1.0.x, V1.1.x, and V3.x implementations are currently supported for the Digest, CBC, GCM, RSA, ECDH key agreement, and EC key generation algorithms. The OpenSSL V1.1.x and V3.x implementations are also supported for the ChaCha20 and ChaCha20-Poly1305 algorithms. The OpenSSL V1.1.1 onwards implementations are supported for the XDH key agreement and XDH key generation algorithms.

+

On Linux® and AIX® operating systems, the OpenSSL 1.0.x, 1.1.x, or 3.x library is expected to be found on the system path. If you use a package manager to install OpenSSL, the system path will be updated automatically. On Windows™ and MacOS® the OpenSSL 3.x library is bundled. Later levels of some Linux operating systems also bundle OpenSSL 3.x.

If you have multiple versions of OpenSSL on your system, the OpenJ9 VM uses the latest version.

-

Note: OpenSSL 3.0.x does not support initialization vector (IV) sizes above 16 Bytes for the GCM algorithm. (In earlier OpenSSL versions, you can use such sizes but they might cause unpredictable behavior.) If you need to use a larger size, disable OpenSSL support for the GCM algorithm.

+

Note: OpenSSL 3.x does not support initialization vector (IV) sizes above 16 Bytes for the GCM algorithm. (In earlier OpenSSL versions, you can use such sizes but they might cause unpredictable behavior.) If you need to use a larger size, disable OpenSSL support for the GCM algorithm.

OpenSSL support is enabled by default for all supported algorithms. If you want to limit support to specific algorithms, a number of system properties are available for tuning the implementation.

Each algorithm can be disabled individually by setting the following system properties on the command line:

@@ -8115,6 +8122,13 @@ New -XX:[+|-]UseZlibNX option added + + +
  • + + Support for OpenSSL 3.x + +
    • @@ -8177,6 +8191,7 @@

    What's new in version 0.41.0

  • Change in behavior of -Xshareclasses:readonly
  • New -XX:[+|-]EnableDynamicAgentLoading option added
  • New -XX:[+|-]UseZlibNX option added
    • +
  • Support for OpenSSL 3.x

    • Features and changes

    Binaries and supported environments

    @@ -8200,6 +8215,8 @@

    New -XX:[+|-]Enable

    For more information, see -XX:[+|-]EnableDynamicAgentLoading.

    New -XX:[+|-]UseZlibNX option added

    AIX® system adds the zlibnx library directory path in the LIBPATH environment variable by default, if it is available in the system. You can control the loading of the zlibnx library by using the -XX:[+|-]UseZlibNX option.

    +

    Support for OpenSSL 3.x

    +

    OpenSSL 3.x is now supported on all operating systems. For more information about OpenSSL support, see Cryptographic operations.

    Known problems and full release information

    To see known problems and a complete list of changes between Eclipse OpenJ9 v0.40.0 and v0.41.0 releases, see the Release notes.

    diff --git a/xxjitserversslcert/index.html b/xxjitserversslcert/index.html index 8259250fc8..bfd4544d43 100644 --- a/xxjitserversslcert/index.html +++ b/xxjitserversslcert/index.html @@ -8108,7 +8108,7 @@

    Syntax

    Explanation

    -

    You can encrypt network communication by using OpenSSL 1.0.x, 1.1.x, or 3.0.x. To enable encryption, specify the private key (<key>.pem) and the certificate (<cert>.pem) at the server:

    +

    You can encrypt network communication by using OpenSSL 1.0.x, 1.1.x, or 3.x. To enable encryption, specify the private key (<key>.pem) and the certificate (<cert>.pem) at the server:

    -XX:JITServerSSLKey=<key>.pem -XX:JITServerSSLCert=<cert>.pem

    and use the certificate at the client: