RFR: 8344149: Remove usage of Security Manager from java.rmi [v2]

Alan Bateman alanb at openjdk.org
Fri Nov 22 07:08:29 UTC 2024


On Mon, 18 Nov 2024 21:57:04 GMT, Stuart Marks <smarks at openjdk.org> wrote:

>> First cut at removal of Security Manager stuff from RMI.
>> 
>> This covers just about every SM-related case in RMI, except for a bit of package checking in MarshalInputStream. This will be handled separately. It's covered by [JDK-8344329](https://bugs.openjdk.org/browse/JDK-8344329).
>> 
>> Further simplifications could be done in RuntimeUtil and NewThreadAction. However, those changes started to become somewhat more intrusive than I'd like for this PR, which is focused on removing security-related stuff. EDIT: I've filed [JDK-8344461](https://bugs.openjdk.org/browse/JDK-8344461) to cover this additional cleanup work.
>
> Stuart Marks has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Update with changes from code review.

src/java.rmi/share/classes/sun/rmi/runtime/NewThreadAction.java line 30:

> 28: import java.security.AccessController;
> 29: import java.security.PrivilegedAction;
> 30: import sun.security.util.SecurityConstants;

Are there any remaining uses of sun.security.util.* in java.rmi? I suspect this is the last one, in which case you can update java.base's module-info to not export this package to java.rmi.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/22129#discussion_r1853379179


More information about the core-libs-dev mailing list