Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8352902

Remove the java.security.debug=scl option

XMLWordPrintable

    • Icon: CSR CSR
    • Resolution: Approved
    • Icon: P4 P4
    • 25
    • security-libs
    • None
    • behavioral
    • minimal
    • You can still specify the `scl` option (it is not an error), it just won't print anything. This is consistent behavior with other SM related debug options we had previously removed in JDK 24.
    • System or security property
    • JDK

      Summary

      Remove the java.security.debug=scl option.

      Problem

      This option dumped the permissions that the SecureClassLoader assigns to ProtectionDomains, but with the disabling of the Security Manager in JDK 24, these permissions are always empty and the debugging has no value.

      Solution

      Remove the java.security.debug=scl option and its usages.

      Specification

      Remove the java.security.debug=scl option from Debug.java and it's usage from src/java.base/share/classes/java/security/SecureClassLoader.java as it's no longer useful without the security manager support.

      If you specify -Djava.security.debug=help on the java command line to see the options for this property, it will no longer include the scl option.

            kthirupattur Koushik Muthukrishnan Thirupattur
            mullan Sean Mullan
            Sean Mullan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: