Java Development Kit (32-bit)

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

Java JDK 8 Update 141 (32-bit)

Java JDK 8 Update 141 (32-bit)
Java Development Kit(也稱為 JDK)包含編譯,調試和運行使用 Java 編程語言編寫的小應用程序和應用程序所需的軟件和工具。 JDK 的主要組件是一組編程工具,包括 javac,jar 和 archiver,它們把相關的類庫打包成一個 JAR 文件。這個工具還有助於管理 JAR 文件,javadoc - 文檔生成器,它自動從源代碼註釋生成文檔,jdb - 調試器,jps - 進程狀態工具,顯示當前 Java 進程的進程信息,javap - 類文件反彙編程序,以及其他許多組件。

JDK 還附帶了一個完整的 Java 運行時環境,通常稱為私有運行時。它由 Java 虛擬機和生產環境中存在的所有類庫以及僅對開發人員有用的附加庫(例如國際化庫和 IDL 庫)組成.

JDK 的內容:

開發工具
(在 bin / 子目錄)將幫助您開發,執行,調試和編寫以 JavaTM 編程語言編寫的程序的工具和實用程序。

Runtime Environment
(在 jre / 子目錄中)供 JDK 使用的 Java 運行時環境(JRE)的實現。 JRE 包括一個 Java 虛擬機(JVM),類庫和其他支持執行用 Java 編程語言編寫的程序的文件.

附加庫
(在 lib / 子目錄中)開發工具需要的附加類庫和支持文件.

Demo 小應用程序和應用程序
(在演示 / 子目錄中)Java 平台編程的示例,包括源代碼。這些包括使用 Swing 和其他 Java 基礎類的示例,以及 Java 平台調試器體系結構.

示例代碼
(在示例子目錄中)帶有源代碼的樣本,用於某些 Java API 的編程。

C 頭文件
(在 include / 子目錄中)支持使用 Java 本地接口,JVM 工具接口和 Java 平台的其他功能進行本機代碼編程的頭文件.

源代碼
(在 src.zip 中)構成 Java 核心 API 的所有類的 Java 編程語言源文件(即 java。*,javax。* 和一些 org。* 包的源文件,但不包括 com.sun。* 包)。此源代碼僅供參考,旨在幫助開發人員學習和使用 Java 編程語言。這些文件不包括平台特定的實現代碼,不能用於重建類庫。要提取這些文件,請使用任何常用的 zip 實用程序。或者,您可以在 JDK 的 bin / 目錄中使用 Jar 實用程序:jar xvf src.zip.

也可以:下載適用於 Mac

的 Java Development Kit

ScreenShot

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

檔案名稱 jdk-8u141-windows-i586.exe
檔案大小 190.95 MB
系統 Windows Vista / Windows 7 / Windows 8 / Windows 10
軟體類型 免費軟體
作者 Oracle
官網 http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
更新日期 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 JDK 8 Update 141 (32-bit) 相關參考資料
Download Java Runtime Environment (32bit) 8 Update 141

The Java Runtime Environment (JRE) is an essential software package developed by Oracle Corporation that enables the execution of Java applications on ...

https://www.filepuma.com

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

2017年7月19日 — The Java Runtime Environment (JRE) is an essential software package developed by Oracle Corporation that enables the execution of Java ...

https://www.filepuma.com

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

Key details about this download · The file will be downloaded from secure FileHorse servers · This file is safe and scanned with 68 antivirus apps (Virus-Total ...

https://www.filehorse.com

Java 8 release changes

A fix included in JDK 8 Update ... Java 8 Update 141 (8u141). Release Highlights. IANA ... bit jre uninstall even when 32 bit JRE was still present on the system.

https://www.java.com

Java 8 發行版本變更

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

https://java.com

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

These Java SE 8 update releases are provided under the Binary Code License (“BCL”). Java SE 8u211 and later updates are available, under the Java SE OTN License ...

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