On 12/2/2010 9:26 PM, Dr Andrew John Hughes wrote:
By default, there is no SecurityManager (getSecurityManager returns null) and
thus
everything is permitted. Once the default instance is installed, you're subject
to java.policy.
The above results are nothing to do with jtreg as the above examples
are all just run with a standard 'java' invocation.
Hm... that's surprising. I believe the testing machine where the test
was developed had some very permissive default security policy, and as
such the problem hasn't been caught.
OK, then the test really needs some change, and the proposed fix looks
good to me.
PS. Although if the enhanced security warning is backported to OpenJDK6,
the test and the fix seem useless. And it's already useless in JDK7.
--
best regards,
Anthony
