Java Development Kit (64-bit)

最新版本 Java JDK 8 Update 121 (64-bit)

Java JDK 8 Update 121 (64-bit)

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

JDK 64 位還附帶了一個完整的 Java 運行時環境,通常稱為私有運行時。它由 Java 虛擬機和生產環境中存在的所有類庫以及僅對開發人員有用的附加庫(例如國際化庫和 IDL 庫)組成。下載 Java 開發工具包離線安裝程序安裝 64bit for Windows

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 平台的其他功能進行本地代碼編程的頭文件。下載 Java 開發工具包離線安裝程序安裝程序 64bit for Windows

源代碼
(在 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 121 (64-bit)

檔案名稱 jdk-8u121-windows-x64.exe
檔案大小 195.51 MB
系統 Windows Vista64 / Windows 7 64 / Windows 8 64 / Windows 10 64
軟體類型 免費軟體
作者 Oracle
官網 http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
更新日期 2017-01-18
更新日誌

What's new in this version:

- Improved protection for JNDI remote class loading

Remote class loading via JNDI object factories stored in naming and directory services is disabled by default. To enable remote class loading by the RMI Registry or COS Naming service provider, set the following system property to the string "true", as appropriate:
- com.sun.jndi.rmi.object.trustURLCodebase
- com.sun.jndi.cosnaming.object.trustURLCodebase

jarsigner -verbose -verify should print the algorithms used to sign the jar:
- The jarsigner tool has been enhanced to show details of the algorithms and keys used to generate a signed JAR file and will also provide an indication if any of them are considered weak.
- Specifically, when "jarsigner -verify -verbose filename.jar" is called, a separate section is printed out showing information of the signature and timestamp (if it exists) inside the signed JAR file, even if it is treated as unsigned for various reasons. If any algorithm or key used is considered weak, as specified in the Security property, jdk.jar.disabledAlgorithms, it will be labeled with "(weak)".

NEW FEATURES:
RMI Better constraint checking:
- RMI Registry and Distributed Garbage Collection use the mechanisms of JEP 290 Serialization Filtering to improve service robustness
- RMI Registry and DGC implement built-in white-list filters for the typical classes expected to be used with each service
- Additional filter patterns can be configured using either a system property or a security property. The "sun.rmi.registry.registryFilter" and "sun.rmi.transport.dgcFilter" property pattern syntax is described in JEP 290 and in <JRE>/lib/security/java.security
- JDK-8156802 (not public)

Add mechanism to allow non-default root CAs to not be subject to algorithm restrictions:
- New certpath constraint: jdkCA*
- In the java.security file, an additional constraint named "jdkCA" is added to the jdk.certpath.disabledAlgorithms property. This constraint prohibits the specified algorithm only if the algorithm is used in a certificate chain that terminates at a marked trust anchor in the lib/security/cacerts keystore. If the jdkCA constraint is not set, then all chains using the specified algorithm are restricted. jdkCA may only be used once in a DisabledAlgorithm expression.
- Example: To apply this constraint to SHA-1 certificates, include the following: SHA1 jdkC

Changes:
- The secure validation mode of the XML Signature implementation has been enhanced to restrict RSA and DSA keys less than 1024 bits by default as they are no longer secure enough for digital signatures. Additionally, a new security property named jdk.xml.dsig.SecureValidationPolicy has been added to the java.security file and can be used to control the different restrictions enforced when the secure validation mode is enabled.
- The secure validation mode is enabled either by setting the xml signature property org.jcp.xml.dsig.secureValidation to true with the javax.xml.crypto.XMLCryptoContext.setProperty method, or by running the code with a SecurityManager.
- If an XML Signature is generated or validated with a weak RSA or DSA key, an XMLSignatureException will be thrown with the message, "RSA keys less than 1024 bits are forbidden when secure validation is enabled" or "DSA keys less than 1024 bits are forbidden when secure validation is enabled."
- Restrict certificates with DSA keys less than 1024 bits:
- DSA keys less than 1024 bits are not strong enough and should be restricted in certification path building and validation. Accordingly, DSA keys less than 1024 bits have been deactivated by default by adding "DSA keySize < 1024" to the "jdk.certpath.disabledAlgorithms" security property. Applications can update this restriction in the security property ("jdk.certpath.disabledAlgorithms") and permit smaller key sizes if really needed (for example, "DSA keySize < 768").

More checks added to DER encoding parsing code:
- More checks are added to the DER encoding parsing code to catch various encoding errors. In addition, signatures which contain constructed indefinite length encoding will now lead to IOException during parsing. Note that signatures generated using JDK default providers are not affected by this change.

Additional access restrictions for URLClassLoader.newInstance:
- Class loaders created by the java.net.URLClassLoader.newInstance methods can be used to load classes from a list of given URLs. If the calling code does not have access to one or more of the URLs and the URL artifacts that can be accessed do not contain the required class, then a ClassNotFoundException, or similar, will be thrown. Previously, a SecurityException would have been thrown when access to a URL was denied. If required to revert to the old behavior, this change can be disabled by setting the jdk.net.URLClassPath.disableRestrictedPermissions system property.

A new configurable property in logging.properties java.util.logging.FileHandler.maxLocks:
- A new "java.util.logging.FileHandler.maxLocks" configurable property is added to java.util.logging.FileHandler.
- This new logging property can be defined in the logging configuration file and makes it possible to configure the maximum number of concurrent log file locks a FileHandler can handle. The default value is 100.
- In a highly concurrent environment where multiple (more than 101) standalone client applications are using the JDK Logging API with FileHandler simultaneously, it may happen that the default limit of 100 is reached, resulting in a failure to acquire FileHandler file locks and causing an IO Exception to be thrown. In such a case, the new logging property can be used to increase the maximum number of locks before deploying the application.
- If not overridden, the default value of maxLocks (100) remains unchanged. See java.util.logging.LogManager and java.util.logging.FileHandler API documentation for more details.

Bug fixes:
Trackpad scrolling of text on OS X 10.12 Sierra is very fast:
- The MouseWheelEvent.getWheelRotation() method returned rounded native NSEvent deltaX/Y events on Mac OS X. The latest macOS Sierra 10.12 produces very small NSEvent deltaX/Y values so rounding and summing them leads to the huge value returned from the MouseWheelEvent.getWheelRotation(). The JDK-8166591 fix accumulates NSEvent deltaX/Y and the MouseWheelEvent.getWheelRotation() method returns non-zero values only when the accumulated value exceeds a threshold and zero value. This is compliant with the MouseWheelEvent.getWheelRotation() specification
- "Returns the number of "clicks" the mouse wheel was rotated, as an integer. A partial rotation may occur if the mouse supports a high-resolution wheel. In this case, the method returns zero until a full "click" has been accumulated."
- For the precise wheel rotation values, use the MouseWheelEvent.getPreciseWheelRotation() method instead
- This release also contains fixes for security vulnerabilities described in the Oracle Java SE Critical Patch Update Advisory

Java JDK 8 Update 121 (64-bit) 相關參考資料
Download Java Development Kit (64bit) 8 Update 121 for ...

2017年1月18日 — Developed by Oracle Corporation, JDK equips developers with all the necessary tools and resources to create, test, and deploy Java applications ...

https://www.filepuma.com

Java 8 release changes

This change updates the JDK providers to use 2048 bits ... Java 8 Update 121 (8u121). Release Highlights. IANA ... The change is applicable to 32 bit and 64 bit ...

https://www.java.com

Java 8 發行版本變更

... JDK 8 將系統特性更新為使用傳統Base64 編碼格式 ... Java 8 Update 121 (8u121) ... 「Java 控制面板」中的 更新 標籤除了32 位元版本以外,還可以讓使用者自動更新已安裝在 ...

https://java.com

Java Development Kit 64-bit for Windows

2021年3月30日 — Download Java Development Kit 64-bit 8 Update 121 for Windows. Fast downloads of the latest free software! Click now.

https://filehippo.com

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

Solaris SPARC 64-bit (SVR4 package), 125.09 MB. jdk ... jdk-8u121-linux-arm64-vfp-hflt.tar.gz. Linux x86 ... jdk-8-solaris-x64.tar.Z. Solaris x64, 93.15 MB. jdk-8 ...

https://www.oracle.com