User account creation filtered due to spam.

Bug 46773

Summary: [METABUG] Calling Policy.setPolicy with a new Policy object has no effect on the DefaultSecurityManager
Product: classpath Reporter: Andrew John Hughes <gnu_andrew>
Component: classpathAssignee: Not yet assigned to anyone <unassigned>
Severity: normal    
Priority: P3    
Version: 0.98   
Target Milestone: ---   
Host: Target:
Build: Known to work:
Known to fail: Last reconfirmed:
Bug Depends on: 46774, 46775    
Bug Blocks:    

Description Andrew John Hughes 2010-12-03 00:29:12 UTC
As shown by running this new Mauve test:

calling setPolicy has no effect on the default SecurityManager implementation provided by GNU Classapath.

This is because VMAccessController creates ProtectionDomain objects using the two argument constructor which uses static permissions.  The four argument constructor should be used instead so the policy is consulted.

Fixing this requires changes in a VM class which seems to have local copies in most Classpath VMs (at least CACAO, gij and jamvm).  This metabug thus tracks fixing the issue separately in both gcj and Classpath's reference copy.
Comment 1 Andrew John Hughes 2010-12-20 20:40:00 UTC
Patched in both GNU Classpath and JamVM.

Reported to:

* JamVM
Comment 2 Andrew John Hughes 2010-12-20 20:40:54 UTC
Above should say 'Patched in both GNU Classpath and GCJ' :-)