RELEASE NOTES FOR: 11.0.28
====================================================================================================

Notes generated: Thu Apr 03 05:23:37 CEST 2025

Hint: Prefix bug IDs with https://bugs.openjdk.org/browse/ to reach the relevant JIRA entry.

JAVA ENHANCEMENT PROPOSALS (JEP):

  None.

RELEASE NOTES:

security-libs/javax.crypto:pkcs11:

    JDK-8293345: Legacy Mechanism Check in SunPKCS11 Provider Is Enhanced with Service Type 

      Native PKCS11 mechanisms which support decryption but not encryption, or signature
      verification but not signing, are considered legacy and are disabled by default. The legacy
      mechanism check in SunPKCS11 provider is enhanced with the service type. For example, prior to
      this fix, a mechanism supporting encryption, decryption, and verification but not signing, is
      considered legacy and can't be used at all. After this fix, the corresponding Cipher service
      using this mechanism is available since both encryption and decryption are supported. However,
      the corresponding Signature service is not since only verification is supported. To bypass the
      legacy mechanism check, set the PKCS11 provider configuration attribute "allowLegacy" to true.
      The default value is false. Note that it is the caller's responsibility to make sure the
      legacy mechanism is not used for the unsupported functionality.

security-libs/java.security:

    JDK-8303770: Removed Baltimore CyberTrust Root Certificate after expiry date

      The following expired root certificate has been removed from the `cacerts` keystore: ``` +
      alias name "baltimorecybertrustca [jdk]"   Distinguished Name: CN=Baltimore CyberTrust Root,
      OU=CyberTrust, O=Baltimore, C=IE ```

    JDK-8309841: Jarsigner Should Print a Warning If an Entry Is Removed

      If an entry is removed from a signed JAR file, there is no mechanism to detect that it has
      been removed using the `JarFile` API, since the `getJarEntry` method returns `null` as if the
      entry had never existed. With this change, the `jarsigner -verify` command analyzes the
      signature files and if some sections do not have matching file entries, it prints out the
      following warning: "This JAR contains signed entries for files that do not exist". Users can
      further find out the names of these entries by adding the `-verbose` option to the command.


ALL FIXED ISSUES, BY COMPONENT AND PRIORITY:

client-libs/2d:
  (P3) JDK-8348596: Update FreeType to 2.13.3

client-libs/java.awt:
  (P4) JDK-8346887: DrawFocusRect() may cause an assertion failure

client-libs/javax.accessibility:
  (P3) JDK-8339728: [Accessibility,Windows,JAWS] Bug in the getKeyChar method of the AccessBridge class

infrastructure/release_eng:
  (P4) JDK-8351099: Bump update version of OpenJDK: 11.0.28

security-libs:
  (P4) JDK-8328957: Update PKCS11Test.java to not use hardcoded path

security-libs/java.security:
  (P3) JDK-8309841: Jarsigner should print a warning if an entry is removed
  (P3) JDK-8303770: Remove Baltimore root certificate expiring in May 2025
  (P4) JDK-8026976: ECParameters, Point does not match field size 
  (P4) JDK-8352302: Test sun/security/tools/jarsigner/TimestampCheck.java is failing

security-libs/javax.crypto:pkcs11:
  (P3) JDK-8293345: SunPKCS11 provider checks on PKCS11 Mechanism are problematic
  (P4) JDK-8331959: Update PKCS#11 Cryptographic Token Interface to v3.1

tools/jar:
  (P4) JDK-8339810: Clean up the code in sun.tools.jar.Main to properly close resources and use ZipFile during extract