Java se development kit 8u301 linux

6 JDK Installation for Linux Platforms

This page describes JDK for Linux system requirements and gives installation instructions for several JDK-Linux combinations.

This page contains these topics:

See «JDK 8 and JRE 8 Installation Start Here» for general information about installing JDK 8 and JRE 8.

For information on enhancements to JDK 8 that relate to the installer, see «Installer Enhancements in JDK 8».

System Requirements

See http://www.oracle.com/technetwork/java/javase/certconfig-2095354.html for information about supported platforms, operating systems, and browsers.

On a 64-bit system, you can download either the 64-bit or the 32-bit version of the Java platform. However, if you are using a 32-bit browser and you want to use the plugin, then you need to install the 32-bit version of the Java platform. To determine which version of Firefox you are running, launch the application, and select the menu item Help -> About Mozilla Firefox. At the bottom of the window is a version string line that contains either «Linux i686» (32-bit) or «Linux x86_64» (64-bit). To setup the Java plugin, see «Manual Installation and Registration of Java Plugin for Linux».

JDK 8 Installation Instructions

This topic describes:

Installation Instructions Notation and Files

For instructions containing the notation version , substitute the appropriate JDK update version number. For example, if you are installing update JDK 8 update release 2, the following string representing the name of the bundle:

Note that, as in the preceding example, the version number is sometimes preceded with the letter u , for example, 8u2 , and sometimes it is preceded with an underbar, for example, jdk1.8.0_02 .

The following table lists the options and instructions for downloading the JDK 8 release on a Linux platform.

Download File and Instructions	Architecture (CPU Type)	Who Can Install
For Linux x64 systems: jdk-8u version -linux-x64.tar.gz «Installation of the 64-bit JDK on Linux Platforms»	Intel — 64-bit	anyone
For Linux aarch64 (64-bit ARM) systems: jdk-8u version -linux-aarch64.tar.gz (version 8u271 and later) «Installation of the 64-bit JDK on Linux Platforms	ARM — 64-bit	anyone
For Linux x86 systems: jdk-8u version -linux-i586.tar.gz «Installation of the 32-bit JDK on Linux Platforms»	Intel — 32-bit	anyone
For Linux x64 systems: jdk-8u version -linux-x64.rpm «Installation of the 64-bit JDK on RPM-based Linux Platforms»	Intel — 64-bit RPM-based Linux	root
For Linux aarch64 (64-bit ARM) systems: jdk-8u version -linux-aarch64.rpm (version 8u271 and later) «Installation of the 64-bit JDK on RPM-based Linux Platforms»	ARM — 64-bit RPM-based Linux	root
For Linux x86 systems: jdk-8u version -linux-i586.rpm «Installation of the 32-bit JDK on RPM-based Linux Platforms»	Intel — 32-bit RPM-based Linux	root

Installation can be performed using either of the following:

Installation of JDK using archive files ( .tar.gz ) allows you to install a private version of the JDK for the current user into any location, without affecting other JDK installations. However, it may involve manual steps to get some of the features to work (for example, the -version: release option of the java command, which allows you to specify the release to be used to run the specified class, requires the correct path to the JDK release under /usr/jdk ).

Installation of JDK using RPM packages allows you to perform a system-wide installation of the JDK for all users, and requires root access.

When you download and install the Java Development Kit (JDK), the associated Java Runtime Environment (JRE) is also installed.

JDK 7u6 and later releases include JavaFX SDK (version 2.2 or later). The JavaFX SDK and Runtime are installed and integrated into the standard JDK directory structure.

Installation of the 64-bit JDK on Linux Platforms

This procedure installs the Java Development Kit (JDK) for 64-bit Linux, using an archive file ( .tar.gz ).

These instructions use the following files:

jdk-8uversion-linux-x64.tar.gz and jdk-8uversion-linux-aarch64.tar.gz (version 8u271 and later) for 64-bit ARM systems.

Download the required file.

Before the file can be downloaded, you must accept the license agreement. The archive file can be installed by anyone (not only root users), in any location that you can write to. However, only the root user can install the JDK into the system location.

Change directory to the location where you would like the JDK to be installed, then move the .tar.gz archive file to the current directory.

Unpack the archive file and install the JDK.

• For x64 — % tar zxvf jdk-8uversion-linux-x64.tar.gz
• For 64-bit ARM system — % tar zxvf jdk-8uversion-linux-aarch64.tar.gz

The Java Development Kit files are installed in a directory called jdk1.8.0_ version in the current directory.

Delete the .tar.gz file if you want to save disk space.

Installation of the 64-bit JDK on RPM-based Linux Platforms

This procedure installs the Java Development Kit (JDK) for 64-bit RPM-based Linux platforms, such as Oracle, Red Hat and SuSE, using an RPM binary file ( .rpm ) in the system location. You must be root to perform this installation.

These instructions use the following files:

jdk-8uversion-linux-x64.rpm and jdk-8uversion-linux-aarch64.rpm (version 8u271 and later) for 64-bit ARM systems.

Download the required file.

Before the file can be downloaded, you must accept the license agreement.

Become root by running su and entering the super-user password.

Uninstall any earlier installations of the JDK packages.

Install the package:

• For x64 — # rpm -ivh jdk-8uversion-linux-x64.rpm
• For 64-bit ARM system — # rpm -ivh jdk-8uversion-linux-aarch64.rpm

To upgrade a package:

• For x64 — # rpm -Uvh jdk-8uversion-linux-x64.rpm
• For 64-bit ARM system — # rpm -Uvh jdk-8uversion-linux-aarch64.rpm

Delete the .rpm file if you want to save disk space.

Exit the root shell. No need to reboot.

Starting with version 8u40, the JDK installation is integrated with the alternatives framework and after installation, the alternatives framework is updated to reflect the binaries from the recently installed JDK. Java commands such as java , javac , javadoc , and javap can be invoked from the command line.

Using the java -version command, users can confirm the default (recently installed) JDK version.

In addition, users can now check which specific RPM package provides the java files:

Change in Communication With the Alternatives Framework of JDK RPM Installer Starting With JDK 8u261

Prior to JDK 8u261, the JDK RPM installers registered two groups of symbolic links with the alternatives framework, java and javac . In some versions of the alternatives framework, certain link names in these groups were duplicated, which resulted in installation failures.

Starting with JDK 8u261, the JDK RPM doesn’t register the javac group with the alternatives framework. All links unique to the javac group are moved into the java group, but the set of symbolic links registered by the installer are not changed; only the duplicated links have been dropped.

The implication of this change is that if you install JDK 8u261 and JDK 8u251 (or older versions) and uninstall JDK 8u261, the symbolic links from the java group that are managed by the alternatives framework will be deleted. To restore the deleted links, run the following command:

Installation of the 32-bit JDK on Linux Platforms

This procedure installs the Java Development Kit (JDK) for 32-bit Linux, using an archive file ( .tar.gz ).

These instructions use the following file:

Download the file.

Before the file can be downloaded, you must accept the license agreement. The archive file can be installed by anyone (not only root users), in any location that you can write to. However, only the root user can install the JDK into the system location.

Change directory to the location where you would like the JDK to be installed, then move the .tar.gz archive file to the current directory.

Unpack the archive file and install the JDK.

The Java Development Kit files are installed in a directory called jdk1.8.0_ version in the current directory.

Delete the .tar.gz file if you want to save disk space.

Installation of the 32-bit JDK on RPM-based Linux Platforms

This procedure installs the Java Development Kit (JDK) for 32-bit RPM-based Linux platforms, such as Red Hat and SuSE, using an RPM binary file ( .rpm ) in the system location. You must be root to perform this installation.

These instructions use the following file:

Download the file.

Before the file can be downloaded, you must accept the license agreement.

Become root by running su and entering the super-user password.

Uninstall any earlier installations of the JDK packages.

Install the package.

To upgrade a package:

Exit the root shell. No need to reboot.

Delete the .rpm file if you want to save disk space.

Starting with version 8u40, the JDK installation is integrated with the alternatives framework and after installation, the alternatives framework is updated to reflect the binaries from the recently installed JDK. Java commands such as java , javac , javadoc , and javap can be invoked from the command line.

Using the java -version command, users can confirm the default (recently installed) JDK version.

In addition, users can now check which specific RPM package provides the java files:

Installation of Public Key on RPM-based Linux Platforms

Since JDK version 8, the JDK RPMs are signed with OL keys. Installation of these RPMs on Linux distributions other than OL gives a warning message indicating that security validation of the package fails. This indicates that the public key used to sign this RPM needs to be installed in the system. A sample warning message and the public key installation steps are as follows:

Sample Warning Message

Installation Steps

Download the key file from https://yum.oracle.com/RPM-GPG-KEY-oracle-ol7 using the following command:

Install the key using the following command:

sudo rpm —import RPM-GPG-KEY-oracle-ol7

Public key installation needs to be done only once. The key installation is persistent across reboots.

General Installation Notes

This topic describes general installation topics.

Root Access

Installing the software automatically creates a directory called jdk1.8.0_ version . Note that if you choose to install the JDK into system-wide location, such as /usr/jdk , you must first become root to gain the necessary permissions. If you do not have root access, simply install the JDK into your home directory, or a subdirectory that you have permission to write to.

Overwriting Files

If you install the software in a directory that contains a subdirectory named jdk1.8.0_ version , the new software overwrites files of the same name in that jdk1.8.0_ version directory. Please be careful to rename the old directory if it contains files you would like to keep.

System Preferences

By default, the installation script configures the system such that the backing store for system preferences is created inside the JDK’s installation directory. If the JDK is installed on a network-mounted drive, it and the system preferences can be exported for sharing with Java runtime environments on other machines.

Источник

JDK 8u301 Update Release Notes

Java™ SE Development Kit 8, Update 301 (JDK 8u301)

The full version string for this update release is 8u301-b09 (where «b» means «build»). The version number is 8u301.

IANA TZ Data 2021a

JDK 8u301 contains IANA time zone data 2021a.

Security Baselines

The security baselines for the Java Runtime Environment (JRE) at the time of the release of JDK 8u301 are specified in the following table:

JRE Family Version JRE Security Baseline (Full Version String) 8 8u301-b09 7 7u311-b07

Keeping the JDK up to Date

Oracle recommends that the JDK is updated with each Critical Patch Update. In order to determine if a release is the latest, the Security Baseline page can be used to determine which is the latest version for each release family.

Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Bulletins. It is not recommended that this JDK (version 8u301) be used after the next critical patch update scheduled for October 19, 2021.

Java SE Subscription customers managing JRE updates/installs for large numbers of desktops should consider using Java Advanced Management Console (AMC).

For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 8u301) on 2021-11-19. After either condition is met (new release becoming available or expiration date reached), the JRE will provide additional warnings and reminders to users to update to the newer version. For more information, see 23.1.2 JRE Expiration Date in the Java Platform, Standard Edition Deployment Guide.

New Features

The support for the Kerberos MSSFU extensions [1] is now extended to cross-realm environments.

By leveraging the Kerberos cross-realm referrals enhancement introduced in the context of JDK-8215032, the ‘S4U2Self’ and ‘S4U2Proxy’ extensions may be used to impersonate user and service principals located on different realms.

New system and security properties have been added to enable users to customize the generation of PKCS #12 keystores. This includes algorithms and parameters for key protection, certificate protection, and MacData. The detailed explanation and possible values for these properties can be found in the «PKCS12 KeyStore properties» section of the java.security file.

Also, support for the following SHA-2 based HmacPBE algorithms has been added to the SunJCE provider: HmacPBESHA224, HmacPBESHA256, HmacPBESHA384, HmacPBESHA512, HmacPBESHA512/224, HmacPBESHA512/256

Removed Features and Options

The following root certificates with weak 1024-bit RSA public keys have been removed from the cacerts keystore:

The following root certificate has been removed from the cacerts truststore:

Other Notes

The following capabilities have been removed from the list of what OracleJDK/OracleJRE RPMs provide: xml-commons-api , jaxp_parser_impl , and java-fonts . This clean-up of the list resolves existing and potential conflicts with modular RPMs.

There are other rpms providing these capabilities, so there should be no impact on packages that depend on them. Package managers can use other RPMs to satisfy the dependencies provided by the OracleJDK/OracleJRE RPMs before this change.

The default encryption algorithms used in a PKCS #12 keystore have been updated. The new algorithms are based on AES-256 and SHA-256 and are stronger than the old algorithms that were based on RC2, DESede, and SHA-1. See the security properties starting with keystore.pkcs12 in the java.security file for detailed information.

For compatibility, a new system property named keystore.pkcs12.legacy is defined that will revert the algorithms to use the older, weaker algorithms. There is no value defined for this property.

Certain TLS ALPN values couldn’t be properly read or written by the SunJSSE provider. This is due to the choice of Strings as the API interface and the undocumented internal use of the UTF-8 character set which converts characters larger than U+00007F (7-bit ASCII) into multi-byte arrays that may not be expected by a peer.

SunJSSE now encodes/decodes String characters as 8-bit ISO_8859_1/LATIN-1 characters. This means applications that used characters above U+000007F that were previously encoded using UTF-8 may need to either be modified to perform the UTF-8 conversion, or set the Java security property jdk.tls.alpnCharset to «UTF-8» revert the behavior.

Client-side FTP support in the Java platform is available through the FTP URL stream protocol handler, henceforth referred to as the FTP Client.

The following system property has been added for validation of server addresses in FTP passive mode.

In this release, the FTP Client has been enhanced to reject an address sent by a server, in response to a PASV command from the FTP Client, when that address differs from the address which the FTP Client initially connected.

To revert to the prior behavior, the jdk.net.ftp.trustPasvAddress system property can be set to true . The affect of setting this property is that the FTP Client accepts and uses the address value returned in reply to a PASV command

Bug Fixes

This release also contains fixes for security vulnerabilities described in the Oracle Critical Patch Update. For a more complete list of the bug fixes included in this release, see the JDK 8u301 Bug Fixes page.

Источник