Skip to content

Conversation

@RogerRiggs
Copy link
Contributor

@RogerRiggs RogerRiggs commented Apr 4, 2025

Now that the Security Manager is permanently disabled, the following permission classes in the core libraries area can be deprecated for removal as they are no longer useful: FilePermission, LinkPermission, LoggingPermission, PropertyPermission, ReflectPermission, RuntimePermission, and SerializablePermission

@deprecated(forRemoval = true, since="25")
Is added to each class and the existing @APinote is converted to @deprected


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change requires CSR request JDK-8353728 to be approved

Issues

  • JDK-8353641: Deprecate core library permission classes for removal (Enhancement - P3)
  • JDK-8353728: Deprecate core library permission classes for removal (CSR)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24444/head:pull/24444
$ git checkout pull/24444

Update a local copy of the PR:
$ git checkout pull/24444
$ git pull https://git.openjdk.org/jdk.git pull/24444/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 24444

View PR using the GUI difftool:
$ git pr show -t 24444

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24444.diff

Using Webrev

Link to Webrev Comment

Now that the Security Manager is permanently disabled, the following permission classes
in the core libraries area can be deprecated for removal as they are no longer useful:
FilePermission, LinkPermission, LoggingPermission, PropertyPermission, ReflectPermission,
RuntimePermission, and SerializablePermission

@deprecated(forRemoval = true, since="25")
Is added to each class and the existing @APinote is converted to @deprected
@RogerRiggs
Copy link
Contributor Author

/csr

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 4, 2025

👋 Welcome back rriggs! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Apr 4, 2025

@RogerRiggs This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8353641: Deprecate core library permission classes for removal

Reviewed-by: mullan, iris

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 90 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot added rfr Pull request is ready for review csr Pull request needs approved CSR before integration labels Apr 4, 2025
@openjdk
Copy link

openjdk bot commented Apr 4, 2025

@RogerRiggs has indicated that a compatibility and specification (CSR) request is needed for this pull request.

@RogerRiggs please create a CSR request for issue JDK-8353641 with the correct fix version. This pull request cannot be integrated until the CSR request is approved.

@openjdk
Copy link

openjdk bot commented Apr 4, 2025

@RogerRiggs The following labels will be automatically applied to this pull request:

  • core-libs
  • net
  • nio
  • security

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added security security-dev@openjdk.org nio nio-dev@openjdk.org core-libs core-libs-dev@openjdk.org net net-dev@openjdk.org labels Apr 4, 2025
@mlbridge
Copy link

mlbridge bot commented Apr 4, 2025

@dfuch
Copy link
Member

dfuch commented Apr 4, 2025

Looks reasonable to me. Changes to LoggingPermission look good. Out of curiosity I also looked at all usages of RuntimePermission in the JDK - I believe you caught them all - including the unexpected use in XSLT.

@seanjmullan
Copy link
Member

Some copyright dates have not been updated.

return is;
}

@SuppressWarnings("removal")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should not be necessary.

*
*/

@Deprecated(forRemoval = true, since="25")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This order is different than other classes, maybe make it consistent?

*/

@Deprecated(since="25", forRemoval=true)
@SuppressWarnings("removal")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this leftover? You already add it to the methods that need it.

* kill threads. Lazily constructed.
*/
@SuppressWarnings("removal")
static volatile RuntimePermission modifyThreadPermission;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be removed, it's not used.

…missions, URLClassLoader.getPermissions.

Remove dead code from ForkJoinPool.
Add @SuppressWarnings("remove")
…r.getPermissions, URLClassLoader.getPermissions."

SecureClassLoader.getPermissions and URLClassLoader.getPermissions are not marked as Deprecated.
@openjdk openjdk bot removed the csr Pull request needs approved CSR before integration label Apr 7, 2025
@openjdk openjdk bot added the ready Pull request is ready to be integrated label Apr 10, 2025
@RogerRiggs
Copy link
Contributor Author

/integrate

@openjdk
Copy link

openjdk bot commented Apr 10, 2025

Going to push as commit af5db51.
Since your change was applied there have been 96 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Apr 10, 2025
@openjdk openjdk bot closed this Apr 10, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Apr 10, 2025
@openjdk
Copy link

openjdk bot commented Apr 10, 2025

@RogerRiggs Pushed as commit af5db51.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core-libs core-libs-dev@openjdk.org integrated Pull request has been integrated net net-dev@openjdk.org nio nio-dev@openjdk.org security security-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

5 participants