RFR (12): 8191053: Provide a mechanism to make system's security manager immutable

Sean Mullan sean.mullan at oracle.com
Tue Oct 2 17:14:23 UTC 2018


On 10/2/18 1:05 PM, Mandy Chung wrote:
> I'm not a fan of using double == which is not obvious to catch the 
> typo.  I think the `==` syntax may not be commonly known either (I 
> suspect it's seldom for a user to override java.security.policy rather 
> than augmenting it).
> 
> Have you considered using simple token `disallow` and `allow` (or 
> all-caps)?

I am fine with that as well.

>  The possibility of a custom security manager class named 
> `disallow` and `allow` should be low.

I agree. I could imagine there might be a custom SM class named 
"Disallow" but that should still work, right?

--Sean



More information about the security-dev mailing list