On 14/09/2018 03:45, mandy chung wrote:
The behavior makes sense, though the name I think is misleading. It
seems not to disallow a security manager, but to disallow the
capability to *set* the security manager. Maybe
"jdk.allowSetSecurityManager" ?
When -Djdk.allowSecurityManager is set at startup, no security manager
is allowed. Most cases a security manager is started via
-Djava.security.manager on the command-line.
Maybe it would be less confusing if the property was named
-Djdk.disableSecurityManager, because AFAICT, it's what it does?
best regards,
-- daniel
