JEP 486 SecurityManager disabling cleanup
Philip Race
philip.race at oracle.com
Fri Nov 15 05:07:56 UTC 2024
To interested parties
JEP 486 disabled the SecurityManager and updated public specs but
consciously avoided
going further, for example removing JDK code that expected a SM might be
in place.
JEP 486 is done, and that's fine.
I am now coordinating efforts to try to remove that expectation of an SM
in the client-libs implementation.
Whatever we can get done in the same release as the SM disabling will be
good for consistency.
I think we can do almost all of it before RDP 1. Fingers crossed.
Bugs and PRs you may see now and very soon will not address everything
but there will be follow-ups.
Soon, very soon, if we get the initial ones focused on doPrivileged
integrated quickly.
A few things I want to do will involve CSRs to deprecate classes and
methods that are obsoleted.
I will deal with those at the right time in the rapid flow of changes.
-phil
More information about the client-libs-dev
mailing list