Java Runtime Environment (32-bit)

最新版本 Java JRE 8 Update 141 (32-bit)

Java JRE 8 Update 141 (32-bit)

Java JRE 8 Update 141 (32-bit)
Java 運行時環境(JRE)允許您玩在線遊戲,與世界各地的人聊天,計算您的抵押貸款興趣,並以三維方式查看圖像,僅舉幾例。這也是企業計算基礎的內聯網應用和其他電子商務解決方案的組成部分。 Java Runtime Environment(JRE)提供庫,Java 虛擬機和其他組件來運行用 Java 編程語言編寫的 applet 和應用程序。另外,兩個關鍵的部署技術是 JRE 的一部分:Java Plug-in,它允許 Applets 在常用瀏覽器中運行; 以及通過網絡部署獨立應用程序的 Java Web Start。許多跨平台應用程序還需要 Java 才能正常運行。從 FileHorse 下載 Java 離線 PC 安裝程序.

Java 是 Sun Microsystems 在 1995 年首次發布的編程語言和計算平台。除非安裝了 Java,否則每天都會創建更多的應用程序和網站。 Java 是快速,安全和可靠的。從筆記本電腦到數據中心,遊戲機到科學超級計算機,手機到互聯網,Java 無處不在! Java 是我們數字生活的核心。它是開展職業生涯,探索人機界面,構建世界上最好的應用程序,以及在各地從車庫到全球組織開創創新的平台。

為什麼要升級到最新的 Java 版本?
最新的 Java 版本包含了重要的增強功能改善在您的機器上運行的 Java 應用程序的性能,穩定性和安全性。安裝此免費更新將確保您的 Java 應用程序繼續安全有效地運行.

當我下載 Java 軟件時,我將得到什麼?
Java 運行時環境(JRE)是您下載 Java 軟件時得到的。 JRE 由 Java 虛擬機(JVM),Java 平台核心類和支持的 Java 平台庫組成。 JRE 是 Java 軟件的運行時部分,您只需在 Web 瀏覽器中運行它即可.

什麼是 Java 插件軟件?
Java 插件軟件是 Java 運行時環境(JRE)的一個組件。 JRE 允許用 Java 編程語言編寫的小程序在各種瀏覽器中運行。 Java 插件軟件不是獨立的程序,不能單獨安裝.

我聽說過 Java 虛擬機和 JVM 這兩個術語。這是 Java 軟件嗎?
Java 虛擬機只是參與 Web 交互的 Java 軟件的一個方面。 Java 虛擬機內置於 Java 軟件下載中,可幫助運行 Java 應用程序.

注意:當您的 Java 安裝完成時,您可能需要重新啟動瀏覽器(關閉所有瀏覽器窗口並重新打開)以啟用 Java 安裝。

也可用:下載 Java 運行時環境 Mac

ScreenShot

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

檔案名稱 jre-8u141-windows-i586.exe
檔案大小 54.56 MB
系統 Windows Vista / Windows 7 / Windows 8 / Windows 10
軟體類型 免費軟體
作者 Oracle
官網 http://www.java.com/en/
更新日期 2017-07-19
更新日誌

What's new in this version:

IANA DATA 2017b:
- JDK 8u141 contains IANA time zone data version 2017b

CERTIFICATE CHANGES:
- Let's Encrypt certificates added to root CAs. One new root certificate has been added

NEW FEATURES:
security-libs/java.security. Improved algorithm constraints checking:
- With the need to restrict weak algorithms usage in situations where they are most vulnerable, additional features have been added when configuring the jdk.certpath.disabledAlgorithms and jdk.jar.disabledAlgorithms security properties in the java.security file.
- jdk.certpath.disabledAlgorithms: The certpath property has seen the most change. Previously it was limited to two Constraint types; either a full disabling of an algorithm by name or a full disabling of an algorithm by the key size when checking certificates, certificate chains, and certificate signatures. This creates configurations that are absolute and lack flexibility in their usage. Three new Constraints were added to give more flexibility in allowing and rejecting certificates.
- "jdkCA" examines the certificate chain termination with regard to the cacerts file. In the case of "SHA1 jdkCA". SHA1's usage is checked through the certificate chain, but the chain must terminate at a marked trust anchor in the cacerts keystore to be rejected. This is useful for organizations that have their own private CA that trust using SHA1 with their trust anchor, but want to block certificate chains anchored by a public CA from using SHA1.
- "denyAfter" checks if the given date is before the current date or the PKIXParameter date. In the case of "SHA1 denyAfter 2018-01-01", before 2018 a certificate with SHA1 can be used, but after that date, the certificate is rejected. This can be used for a policy across an organization that is phasing out an algorithm with a drop-dead date. For signed JAR files, the date is compared against the TSA timestamp. The date is specified in GMT.

"usage" examines the specified algorithm for a specified usage. This can be used when disabling an algorithm for all usages is not practical. There are three usages that can be specified:
- TLSServer' restricts the algorithm in TLS server certificate chains when server authentication is performed as a client
- TLSClient' restricts the algorithm in TLS client certificate chains when client authentication is performed as a server
- SignedJAR' restricts the algorithms in certificates in signed JAR files. The usage type follows the keyword and more than one usage type can be specified with a whitespace delimiter
- For example, "SHA1 usage TLSServer TLSClient" would disallow SHA1 certificates for TLSServer and TLSClient operations, but SignedJars would be allowed
- All of these constraints can be combined to constrain an algorithm when delimited by '&'. For example, to disable SHA1 certificate chains that terminate at marked trust anchors only for TLSServer operations, the constraint would be "SHA1 jdkCA & usage TLSServer"
- jdk.jar.disabledAlgorithms: One additional constraint was added to this .jar property to restrict JAR manifest algorithms
- "denyAfter" checks algorithm constraints on manifest digest algorithms inside a signed JAR file. The date given in the constraint is compared against the TSA timestamp on the signed JAR file. If there is no timestamp or the timestamp is on or after the specified date, the signed JAR file is treated as unsigned. If the timestamp is before the specified date, the .jar will operate as a signed JAR file. The syntax for restricting SHA1 in JAR files signed after January 1st 2018 is: "SHA1 denyAfter 2018-01-01". The syntax is the same as that for the certpath property, however certificate checking will not be performed by this property

CHANGES:
core-svc/java.lang.management. JMX Diagnostic improvements:
- com.sun.management.HotSpotDiagnostic::dumpHeap API is modified to throw IllegalArgumentException if the supplied file name does not end with “.hprof” suffix. Existing applications which do not provide a file name ending with the “.hprof” extension will fail with IllegalArgumentException. In that case, applications can either choose to handle the exception or restore old behavior by setting system property 'jdk.management.heapdump.allowAnyFileSuffix' to true.

security-libs/javax.net.ssl. Custom HostnameVerifier enables SNI extension:
- Earlier releases of JDK 8 Updates didn't always send the Server Name Indication (SNI) extension in the TLS ClientHello phase if a custom hostname verifier was used. This verifier is set via the setHostnameVerifier(HostnameVerifier v) method in HttpsURLConnection. The fix ensures the Server Name is now sent in the ClientHello body.

xml/jax-ws. Tighter secure checks on processing WSDL files by wsimport tool:

The wsimport tool has been changed to disallow DTDs in Web Service descriptions, specifically:
- DOCTYPE declaration is disallowed in documents
- External general entities are not included by default
- External parameter entities are not included by default
- External DTDs are completely ignored

To restore the previous behavior:
- Set the System property com.sun.xml.internal.ws.disableXmlSecurity to true
- Use the wsimport tool command line option –disableXmlSecurity
- NOTE: JDK 7 and JDK 6 support for this option in wsimport will be provided via a Patch release post July CPU

BUG FIXES:
- JFileChooser with Windows look and feel crashes on win 10
- Race Condition in java.lang.reflect.WeakCache
- java.nio.Bits.unaligned() doesn't return true on ppc
- After updating to Java8u131, the bind to rmiregistry is rejected by registryFilter even though registryFilter is set
- sun.management.LazyCompositeData.isTypeMatched() fail for composite types with items of ArrayType
- SafePointNode::_replaced_nodes breaks with irreducible loops
- NPE when JavaFX loads default stylesheet or font families if CCL is null
- WebEngine.getDocument().getDocumentURI() no longer returns null for loading a String of HTML
- Failed to load RSA private key from pkcs12
- Improved algorithm constraints checking
- Custom HostnameVerifier disables SNI extension

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

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 141 ...

2017年7月19日 — 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 141 ...

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

https://filehippo.com

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

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

https://www.filehorse.com

Java 8 發行版本變更

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

https://java.com

Java JRE 8 update 141 SHA Mismatch - Patch

2017年8月2日 — After manually caching the executables via a SHA1 calculator, I can see that there appears to be a SHA1 mismatch: 32-bit fixlet:

https://forum.bigfix.com

Java Runtime Environment 8.0 build 141 (32-bit)

Download Java Runtime Environment 8.0 build 141 (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 141

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