[patch #1031] [Patch #1031] SecurityManager to use VM interface for current classloader

[noreply]

Patch #1031 has been updated. 

Project: 
Category: None
Status: Closed
Summary: SecurityManager to use VM interface for current classloader

Follow-Ups:

Date: Sun 02/02/03 at 00:56
By: cbj

Comment:
This patch would seem to bypass the security checks involved with this 
deprecated method in SecurityManager.  Looking at this patch makes me believe 
that Class.java needs to be updated with regards to what are "core" classes and 
should return "null".  Also you already have a chance to influence this method 
using VMSecurityManager.getClassContext().
-------------------------------------------------------

Date: Sat 08/09/03 at 23:11
By: mark

Comment:
How important is this to get in before 0.06 is released?

We really need to set this up so all of inClass(String), classDepth(String), 
classLoaderDepth(), currentClassLoader(), currentLoadedClass() and 
getClassContext() are handled likewise.
-------------------------------------------------------

Date: Thu 08/14/03 at 14:03
By: mark

Comment:
David Grove said on the mailinglist:

I talked to Julian, and Jikes RVM no longer has a functional need for this 
particular patch.  In the long run, getting a nice break between 
SecurityManager and a VMSecurityManager would be good for our performance, but 
the current code is functionally ok. Our suggestion would be to cancel this 
particular patch in favor of a more complete refactoring of this code to get a 
nice VMSecurityManager class we could provide our own implementation of after 
0.06 come out.

-------------------------------------------------------

-------------------------------------------------------
For more info, visit:

http://savannah.gnu.org/patch/?func=detailpatch&patch_id=1031&group_id=85

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/