Menu
Jun 19, 2016 This page is not a recommendation to remove Java 8 Update 51 by Oracle Corporation from your computer, we are not saying that Java 8 Update 51 by Oracle Corporation is not a good application. This text simply contains detailed info on how to. Jul 16, 2015 Java Runtime Environment (JRE) is Java’s most basic virtual machine. Download our free update detector to keep your software up to date Share This Page. Home Developer Tools Java Software Java Runtime Environment (32bit) 8 Update 51 Tweet. Latest Version Java Runtime Environment (32bit) 8.0.2210.11 Old Versions Java Runtime.
Find related downloads to Java 1.1.8.2 freeware and softwares, download Java Runtime Environment, Java Runtime Environment, Line, ArgoUML, Adobe Reader, thinkDesktop. Download Java JRE 8 Update 51 (32-bit) for PC from FileHorse. 100% Safe and Secure Free Download 32-bit Software Version. Java manual download page. Get the latest version of the Java Runtime Environment (JRE) for Windows, Mac, Solaris, and Linux. Download Help. Java Downloads for All Operating Systems Recommended Version 8 Update 221 Release date July 16, 2019. Jul 15, 2015 Download This Version (41.22MB) Download Advertisement. Latest Version Java Runtime Environment 8.0 build 201 (64-bit) for PC Windows Older Versions. Java Plug-in technology, included as part of the Java 2 Runtime Environment, Standard Edition (JRE), establishes a connection between popular browsers and the Java platform.
Java™ SE Development Kit 8, Update 51 (JDK 8u51)
The full version string for this update release is 1.8.0_51-b16 (where 'b' means 'build'). The version number is 8u51.
Highlights
This update release contains several enhancements and changes including the following:
IANA Data 2015d
JDK 8u51 contains IANA time zone data version 2015d. For more information, refer to Timezone Data Versions in the JRE Software.
Security Baselines
The security baselines for the Java Runtime Environment (JRE) at the time of the release of JDK 8u51 are specified in the following table:
JRE Family Version | JRE Security Baseline (Full Version String) |
---|---|
8 | 1.8.0_51 |
7 | 1.7.0_85 |
6 | 1.6.0_101 |
For more information about security baselines, see Deploying Java Applets With Family JRE Versions in Java Plug-in for Internet Explorer.
JRE Expiration Date
The JRE expires whenever a new release with security vulnerability fixes becomes available. Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Third Party Bulletin. This JRE (version 8u51) will expire with the release of the next critical patch update scheduled for October 20, 2015.
For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 8u51) on November 20, 2015. 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 JRE Expiration Date.
New Features and Changes
Ephemeral DH keys less than 768 bits deactivated
Ephemeral DH keys less than 768 bits are deactivated in JDK. New algorithm restriction DH keySize < 768 is added to Security Property jdk.tls.disabledAlgorithms.
Ephemeral DH keys less than 768 bits are deactivated in JDK. New algorithm restriction DH keySize < 768 is added to Security Property jdk.tls.disabledAlgorithms.
JDK-8076328 (not public).
Operating system's restricted environment (Native Sandbox)
JDK 8u51 introduced the following changes to Native Sandbox:
- Native sandbox is available on Windows platform only.
- Native sandbox can be enabled or disabled through Java Control Panel->Advanced settings->Enable the operating system's restricted environment (native sandbox) or by setting
deployment.security.use.native.sandbox
property to true indeployment.properties
file.Native sandbox is disabled by default. - When native sandbox is enabled, the sandbox applets or web-start applications will run in a restricted environment, that is provided by the operating system. This will not affect the all-permission applications and they will continue to run as before.
- Native sandbox will be disabled for applications included the in Exception Site List (ESL) or when Deployment Rule Set (DRS) is used.
- Sandbox applets deployed with HTML applet tag which includes all-permissions JAR files from the
Class-Path
manifest attribute, will run in native sandbox.In such cases, a special warning dialog will display, informing the user that the applet may not work properly, when such an applet tries to access the all-permission JAR files. - Custom preloader will be disabled in certain cases when native sandbox is enabled:
- Custom preloader will be disabled when sandbox applets or web-start applications are initializing and the default preloader will be used instead. After application is initialized, Java VM restarts with native sandbox enabled and the custom preloader will be used.
- For all-permission applications, custom preloader will be disabled if it is located in the JNLP file with sandbox permission, until user agrees to run application from the Security Dialog, which grants unrestricted access (privileged) to application.
Bug Fixes
This release contains fixes for security vulnerabilities. For more information, see Oracle Critical Patch Update Advisory.
For a list of bug fixes included in this release, see JDK 8u51 Bug Fixes page.
The following are some of the notable bug fixes included in this release:
Area: security-libs/java.security
Synopsis: Add new Comodo roots to root CAs
Synopsis: Add new Comodo roots to root CAs
Four new root certificates have been added for Commodo:
JDK-8077652 (not public)
Area: security-libs/java.security
Synopsis: Add new GlobalSign roots to root CAs
Synopsis: Add new GlobalSign roots to root CAs
Two root certificates have been added for GlobalSign:
JDK-8077653 (not public)
Area: security-libs/java.security
Synopsis: Add Actalis to root CAs
Synopsis: Add Actalis to root CAs
Added one new root certificate:
JDK-8077651 (not public)
Area: security-libs/java.security
Synopsis: Add new Entrust ECC root
Synopsis: Add new Entrust ECC root
Added one new root certificate:
JDK-8072961 (not public)
Area: security-libs/java.security
Synopsis: Remove old Valicert Class 1 and 2 Policy roots
Synopsis: Remove old Valicert Class 1 and 2 Policy roots
Removed two root certificates with 1024-bit keys:
JDK-8077354 (not public)
Area: security-libs/java.security
Synopsis: Remove old Thawte roots
Synopsis: Remove old Thawte roots
Removed two root certificates with 1024-bit keys:
JDK-8073271 (not public)
Area: security-libs/java.security
Synopsis: Remove more old Verisign, Equifax, and Thawte roots
Synopsis: Remove more old Verisign, Equifax, and Thawte roots
Removed five root certificates with 1024-bit keys:
JDK-8075091 (not public)
Area: security-libs/java.security
Synopsis: Remove TrustCenter CA roots from cacerts
Synopsis: Remove TrustCenter CA roots from cacerts
Removed three root certificates:
JDK-8071699 (not public)
Area: security-libs/javax.net.ssl
Synopsis: Deprecate RC4 in SunJSSE provider
Synopsis: Deprecate RC4 in SunJSSE provider
RC4 is now considered as a weak cipher. Servers should not select RC4 unless there is no other stronger candidate in the client requested cipher suites. A new security property,
jdk.tls.legacyAlgorithms
, is added to define the legacy algorithms in Oracle JSSE implementation. RC4 related algorithms are added to the legacy algorithms list.JDK-8043201 (not public)
Area: security-libs/javax.net.ssl
Synopsis: Prohibit RC4 cipher suites
Synopsis: Prohibit RC4 cipher suites
RC4 is now considered as a compromised cipher. RC4 cipher suites have been removed from both client and server default enabled cipher suite list in Oracle JSSE implementation. These cipher suites can still be enabled by SSLEngine.setEnabledCipherSuites() and SSLSocket.setEnabledCipherSuites() methods.
JDK-8043202 (not public)
Area: security-libs/javax.net.ssl
Synopsis: Improved certification checking
Synopsis: Improved certification checking
With this fix, JSSE endpoint identification does not perform reverse name lookup for IP addresses by default in JDK.
If an application does need to perform reverse name lookup for raw IP addresses in SSL/TLS connections, and encounter endpoint identification compatibility issue, System property 'jdk.tls.trustNameService' can be used to switch on reverse name lookup. Note that if the name service is not trustworthy, enabling reverse name lookup may be susceptible to MITM attacks.
JDK-8067694 (not public)
Known Issues
Area: deploy/plugin
Synopsis: Java issue with Firefox 38, long delay with MyD loading
Synopsis: Java issue with Firefox 38, long delay with MyD loading
Java Plugin is unable to obtain proxy settings from Firefox 38 due to a bug in Mozilla framework. It may cause a long delay during RIA start up or can even cause start up failures. See the related issue:
According to Mozilla, Firefox 39 will contain a fix for this problem.
Workarounds:
Java Version 8 Update 51
- Use another supported browser
- Downgrade browser to Firefox 37
- Specify proxy settings in JCP (NOT in 'Browser settings')
Java Version 7 Update 51
JDK-8081459 (not public)
Area: deploy
Synopsis: JNLP files won't launch from IE11 on Windows 10 Creators Update
Synopsis: JNLP files won't launch from IE11 on Windows 10 Creators Update
Web-start applications cannot be launched when clicking JNLP link from IE 11 on Windows 10 Creators Update when 64-bit JRE is installed. Workaround is to uninstall 64-bit JRE and use only 32-bit JRE.
Java 7 Update 51 Download
See JDK-8185661.