Unless there is a phone home mechanism built into the SecurityManager,
nobody knows or can claim to know how widely the SecurityManager is being
used.
No, survey results don’t prove anything because people don’t fill in
surveys. No, calls for people to report on their usage don’t mean anything
in
We have updated the JEP with a few changes to the "Issue Warnings"
section [1], summarized as follows:
If the Java runtime is started without setting the system property
'java.security.manager' then a custom Security Manager can be installed
dynamically by calling System::setSecurityManager, just
Also, from the point of view of Apache NetBeans, here’s a list of our
concerns with these developments:
https://blogs.apache.org/netbeans/entry/jep-411-deprecate-the-security
Apache NetBeans doesn't use java.lang.SecurityManager to guarantee
security, but rather to gain additional insight into
