[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Default Policy
From: |
Jeroen Frijters |
Subject: |
RE: Default Policy |
Date: |
Sat, 13 Aug 2005 10:57:48 +0200 |
Casey Marshall wrote:
> Bug classpath/22853 prompted this, btw.
>
> Kaffe and jamvm should (I posted patches for both of these);
> probably gcj (I posted a patch for this too, but it's been
> hit-or-miss on whether or not my GCJ patches are accepted); I
> think I remember reading that IKVM implements it;
IKVM supports VMAccessController (and I originally filed 22853).
> I remember discussion some time ago about supporting a similar thing
> in Classpath -- so if 'java.security.manager' is defined, but empty,
> we use the default security manager. If non-empty we take the value
> as a class that extends SecurityManager, and load and instantiate
> that as the security manager.
This is already how it is currently implemented in Classpath. The code
to instantiate the default or specified security manager lives in
java/lang/ClassLoader.java (for bootstraping reasons).
Regards,
Jeroen
- Default Policy, Casey Marshall, 2005/08/09
- RE: Default Policy,
Jeroen Frijters <=