Java JRE 8 Update 131 (32-bit) 軟體 Download 下載

檔案名稱 jre-8u131-windows-i586.exe

Java JRE 8 Update 131 (32-bit) 軟體下載

軟體資訊
檔案版本 Java JRE 8 Update 131 (32-bit)

檔案名稱 jre-8u131-windows-i586.exe
檔案大小 54.83 MB
更新日期 2017-04-18
  • 1
    版本確認
  • 2
    檔案準備中
  • 3
    檔案下載

軟體介紹 & 更新資訊

Java JRE 8 Update 131 (32-bit)
Java 運行時環境(JRE)允許您玩在線遊戲,與世界各地的人聊天,計算您的抵押貸款興趣,並以三維方式查看圖像,僅舉幾例。這也是企業計算基礎的內聯網應用和其他電子商務解決方案的組成部分。 Java Runtime Environment(JRE)提供庫,Java 虛擬機和其他組件來運行用 Java 編程語言編寫的 applet 和應用程序。另外,兩個關鍵的部署技術是 JRE 的一部分:Java P... Java Runtime Environment (32-bit) 軟體介紹

What's new in this version:

CHANGES:
MD5 added to jdk.jar.disabledAlgorithms Security property:
This JDK release introduces a new restriction on how MD5 signed JAR files are verified. If the signed JAR file uses MD5, signature verification operations will ignore the signature and treat the JAR as if it were unsigned. This can potentially occur in the following types of applications that use signed JAR files:
- Applets or Web Start Applications
- Standalone or Server Applications that are run with a SecurityManager enabled and are configured with a policy file that grants permissions based on the code signer(s) of the JAR file.
- The list of disabled algorithms is controlled via the security property, jdk.jar.disabledAlgorithms, in the java.security file. This property contains a list of disabled algorithms and key sizes for cryptographically signed JAR files.
- To check if a weak algorithm or key was used to sign a JAR file, one can use the jarsigner binary that ships with this JDK. Running "jarsigner -verify" on a JAR file signed with a weak algorithm or key will print more information about the disabled algorithm or key.

New system property to control caching for HTTP SPNEGO connection:
- A new JDK implementation specific system property to control caching for HTTP SPNEGO (Negotiate/Kerberos) connections is introduced. Caching for HTTP SPNEGO connections remains enabled by default, so if the property is not explicitly specified, there will be no behavior change.
- When connecting to an HTTP server that uses SPNEGO to negotiate authentication, and when connection and authentication with the server is successful, the authentication information will then be cached and reused for further connections to the same server. In addition, connecting to an HTTP server using SPNEGO usually involves keeping the underlying connection alive and reusing it for further requests to the same server. In some applications, it may be desirable to disable all caching for the HTTP SPNEGO (Negotiate/Kerberos) protocol in order to force requesting new authentication with each new request to the server.

With this change, we now provide a new system property that allows control of the caching policy for HTTP SPNEGO connections. If jdk.spnego.cache is defined and evaluates to false, then all caching will be disabled for HTTP SPNEGO connections. Setting this system property to false may, however, result in undesirable side effects:
- Performance of HTTP SPNEGO connections may be severely impacted as the connection will need to be re-authenticated with each new request, requiring several communication exchanges with the server.
- Credentials will need to be obtained again for each new request, which, depending on whether transparent authentication is available or not, and depending on the global Authenticator implementation, may result in a popup asking the user for credentials for every new request.

New system property to control caching for HTTP NTLM connection:
- A new JDK implementation specific system property to control caching for HTTP NTLM connection is introduced. Caching for HTTP NTLM connection remains enabled by default, so if the property is not explicitly specified, there will be no behavior change.
- On some platforms, the HTTP NTLM implementation in the JDK can support transparent authentication, where the system user credentials are used at system level. When transparent authentication is not available or unsuccessful, the JDK only supports getting credentials from a global authenticator. If connection to the server is successful, the authentication information will then be cached and reused for further connections to the same server. In addition, connecting to an HTTP NTLM server usually involves keeping the underlying connection alive and reusing it for further requests to the same server. In some applications, it may be desirable to disable all caching for the HTTP NTLM protocol in order to force requesting new authentication with each new requests to the server.

With this change, we now provide a new system property that allows control of the caching policy for HTTP NTLM connections. If jdk.ntlm.cache is defined and evaluates to false, then all caching will be disabled for HTTP NTLM connections. Setting this system property to false may, however, result in undesirable side effects:
- Performance of HTTP NTLM connections may be severely impacted as the connection will need to be re-authenticated with each new request, requiring several communication exchanges with the server.
- Credentials will need to be obtained again for each new request, which, depending on whether transparent authentication is available or not, and depending on the global Authenticator implementation, may result in a popup asking the user for credentials for every new request.

New version of VisualVM:
- VisualVM 1.3.9 was released on October 4th, 2016 and has been integrated into 8u131

BUG FIXES:
Correction of IllegalArgumentException from TLS handshake:
- A recent issue from the JDK-8173783 fix can cause issue for some TLS servers. The problem originates from an IllegalArgumentException thrown by the TLS handshaker code: java.lang.IllegalArgumentException: System property jdk.tls.namedGroups(null) contains no supported elliptic curves. The issue can arise when the server doesn't have elliptic curve cryptography support to handle an elliptic curve name extension field (if present). Users are advised to upgrade to this release. By default, JDK 7 Updates and later JDK families ship with the SunEC security provider which provides elliptic curve cryptography support. Those releases should not be impacted unless security providers are modified

Java JRE 8 Update 131 (32-bit) 相關參考資料
Download Java Runtime Environment (32bit) 8 Update 131

Strong security measures. Automatic garbage collection for memory management. Support for multi-threading. Write Once, Run Anywhere portability. Just-In-Time ...

https://www.filepuma.com

Download Java Runtime Environment (32bit) 8 Update 131 ...

2017年4月18日 — Furthermore, the JRE incorporates automatic memory management, garbage collection, and security mechanisms to protect against potential threats ...

https://www.filepuma.com

Download Java Runtime Environment 32-bit 8.0 build 131 ...

2022年8月16日 — Download Java Runtime Environment 32-bit 8.0 build 131 for Windows. Fast downloads of the latest free software! Click now.

https://filehippo.com

Downloading Java JRE 8 Update 131 (32-bit) ...

With Java (JRE) you can run Java applications on your Windows PC! · Java JRE 8 Update 131 (32-bit) · Key details about this download.

https://www.filehorse.com

Java 8 發行版本變更

Java 8 Update 131 (8u131). 發行版本重點. IANA Data 2016j ... 自JDK 8u40 發行版本起,如果32 位元JRE 存在的話 ... 「Java 控制面板」中的 更新 標籤除了32 位元版本 ...

https://java.com

Java Downloads for Windows

Java manual download page for Windows. Get the latest version of the Java Runtime Environment (JRE) for Windows.

https://www.java.com

Java Runtime Environment 8.0 build 131 (32-bit)

Download Java Runtime Environment 8.0 build 131 (32-bit) free for Windows PC from FileSoul.com. ✓ Download 100% Free, Safe and Secure software.

https://www.filesoul.com

Java SE 8 Archive Downloads (JDK 8u202 and earlier)

For production use Oracle recommends downloading the latest JDK and JRE versions and allowing auto-update. ... Solaris SPARC 64-bit (SVR4 package) ... Linux ARM 32 ...

https://www.oracle.com

Java SE Embedded 8 Update 131

Starting with the 8u33 release, SE Embedded releases will no longer include PowerPC platforms. Both the 32-bit PPC platforms (e500v2 and e600) that were ...

https://www.oracle.com

下載適用於所有作業系統的Java

2024年4月16日 — Java 軟體手動下載頁面。取得Windows、Solaris 以及Linux 專用的最新版本Java Runtime Environment (JRE)。包括Apple Mac 作業系統平台連結。

https://www.java.com