RFR: 8344233: Remove calls to SecurityManager and doPrivileged in java.net.ProxySelector and sun.net.spi.DefaultProxySelector after JEP 486 integration

[Sean Mullan]

On Fri, 15 Nov 2024 11:37:55 GMT, Jaikiran Pai <jpai at openjdk.org> wrote:

> > No CSR needed for removing those permissions. There's no visible change to the public APIs, and no behavior change that was not already covered by JEP 486 CSR, since permissions checks have now become deadcode. Or am I missing something?
> 
> I believe you are right. The `Permission` classes themselves haven't been deprecated, so I was just curious whether the removal of these named permissions that relate to such classes need to be handled in any specific manner.

Those permission target names have already been removed from `NetPermission` and were listed as removed in the [JEP 486 CSR](https://bugs.openjdk.org/browse/JDK-8338412) - see the text that starts with "The standard permission target names of several subclasses ...". So no CSR should be needed.

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

PR Comment: https://git.openjdk.org/jdk/pull/22145#issuecomment-2479410066