[Bug libgcj/46774] New: [gcj] Calling Policy.setPolicy with a new Policy object has no effect on the DefaultSecurityManager

[Bug libgcj/46774] New: [gcj] Calling Policy.setPolicy with a new Policy object has no effect on the DefaultSecurityManager

[gnu_andrew at member dot fsf.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46774

           Summary: [gcj] Calling Policy.setPolicy with a new Policy
                    object has no effect on the DefaultSecurityManager
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libgcj
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: gnu_andrew@member.fsf.org


VMAccessController creates PermissionDomain objects with the two-argument
constructor, with the result that the default SecurityManager does not check
the system policy.  See PR46773 for more details.

gcj has a local copy of this class so a separate fix is required to that for
GNU Classpath.

[Bug libgcj/46774] [gcj] Calling Policy.setPolicy with a new Policy object has no effect on the DefaultSecurityManager

[gnu_andrew at member dot fsf.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46774

Andrew John Hughes <gnu_andrew at member dot fsf.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |46773

--- Comment #1 from Andrew John Hughes <gnu_andrew at member dot fsf.org> 2010-12-03 00:35:09 UTC ---
Add metabug.

[Bug libgcj/46774] [gcj] Calling Policy.setPolicy with a new Policy object has no effect on the DefaultSecurityManager

[gandalf at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46774

--- Comment #2 from gandalf at gcc dot gnu.org <gandalf at gcc dot gnu.org> 2010-12-16 19:48:12 UTC ---
Author: gandalf
Date: Thu Dec 16 19:48:07 2010
New Revision: 167952

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=167952
Log:
PR libgcj/46774: Create dynamic ProtectionDomain instances which check the
system policy.

2010-12-13  Andrew John Hughes  <ahughes@redhat.com>

    PR libgcj/46774
    * libjava/java/security/VMAccessController.java:
    (DEFAULT_CONTEXT): Create ProtectionDomain with
    four argument constructor (arguments are the same
    as those implied by the two argument constructor).
    (getContext()): Create ProtectionDomain instances
    with four argument constructor using a null Principal
    array (as before) but including the classloader, which
    was always null before.


Modified:
    trunk/libjava/ChangeLog
    trunk/libjava/classpath/lib/java/security/VMAccessController.class
    trunk/libjava/java/security/VMAccessController.java

[Bug libgcj/46774] [gcj] Calling Policy.setPolicy with a new Policy object has no effect on the DefaultSecurityManager

[gandalf at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46774

--- Comment #3 from gandalf at gcc dot gnu.org <gandalf at gcc dot gnu.org> 2010-12-20 18:19:57 UTC ---
Author: gandalf
Date: Mon Dec 20 18:19:52 2010
New Revision: 168092

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=168092
Log:
PR libgcj/46774: Create dynamic ProtectionDomain instances which check the
system policy.

2010-12-13  Andrew John Hughes  <ahughes@redhat.com>

        PR libgcj/46774
        * libjava/java/security/VMAccessController.java:
        (DEFAULT_CONTEXT): Create ProtectionDomain with
        four argument constructor (arguments are the same
        as those implied by the two argument constructor).
        (getContext()): Create ProtectionDomain instances
        with four argument constructor using a null Principal
        array (as before) but including the classloader, which
        was always null before.


Modified:
    branches/gcc-4_5-branch/libjava/ChangeLog
   
branches/gcc-4_5-branch/libjava/classpath/lib/java/security/VMAccessController.class
    branches/gcc-4_5-branch/libjava/java/security/VMAccessController.java

[Bug libgcj/46774] [gcj] Calling Policy.setPolicy with a new Policy object has no effect on the DefaultSecurityManager

[gnu_andrew at member dot fsf.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46774

Andrew John Hughes <gnu_andrew at member dot fsf.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
            Version|4.6.0                       |4.5.1
         Resolution|                            |FIXED
   Target Milestone|---                         |4.5.3

--- Comment #4 from Andrew John Hughes <gnu_andrew at member dot fsf.org> 2010-12-20 18:32:25 UTC ---
Fixed in trunk and 4.5 branch.