[Bug classpath/23916] java.security.AccessControlContext forget Subject in Subject.doAs* methods

[csm at gnu dot org]

------- Additional Comments From csm at gnu dot org  2005-09-24 06:14 -------
I put a little more thought into this, and I think the correct behavior for 
VMAccessController is to:

  - Use the DomainCombiner specified in the last AccessControlContext on the 
stack, if one is specified, 
or
  - Use IntersectingDomainCombiner otherwise

This should be secure because untrusted code cannot (per the standard -- this 
is not implemented yet 
in Classpath) instantiate an AccessControlContext with an arbitrary 
DomainCombiner. Therefore only 
trusted DomainCombiners, such as SubjectDomainCombiner for JAAS, or our default 
one, will ever be 
used.

I think it's probably wrong to return an AccessControlContext that returns our 
IntersectingDomainCombiner instance, if no other is specified. Sun's 
implementation returns null if 
there is no explicit DomainCombiner, and we should follow that behavior, while 
still creating the 
intersection of the stack's permissions with the specified ones.

And, since Classpath strives to be 1.4 (and eventually 1.5) compliant, it must 
support JAAS.

I'll look into fixing these.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |csm at gnu dot org
                   |dot org                     |
             Status|NEW                         |ASSIGNED


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