[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Moving system properties to gnu.classpath.*
From: |
Jeroen Frijters |
Subject: |
RE: Moving system properties to gnu.classpath.* |
Date: |
Tue, 12 Oct 2004 08:52:16 +0200 |
David Holmes wrote:
> That said, given the check only comes into play when a
> security manager is installed, and it may be avoided by a
> user-defined classloader, does this actually provide the
> protection that was desired?
I'm pretty sure the check *cannot* be circumvented by a user-defined
class loader. It may not do the check itself, but that only means it can
load a class in another package (that happens to have the same name).
For it to load bootstrap classes, it will need to delegate to the system
class loader and that's the one doing the checking.
Regards,
Jeroen
- Re: Moving system properties to gnu.classpath.*, (continued)
- Re: Moving system properties to gnu.classpath.*, Archie Cobbs, 2004/10/11
- RE: Moving system properties to gnu.classpath.*, David Holmes, 2004/10/11
- Re: Moving system properties to gnu.classpath.*, Archie Cobbs, 2004/10/11
- RE: Moving system properties to gnu.classpath.*, David Holmes, 2004/10/11
- Re: Moving system properties to gnu.classpath.*, Archie Cobbs, 2004/10/12
RE: Moving system properties to gnu.classpath.*, Jeroen Frijters, 2004/10/11
RE: Moving system properties to gnu.classpath.*, Jeroen Frijters, 2004/10/12
RE: Moving system properties to gnu.classpath.*, Jeroen Frijters, 2004/10/12
RE: Moving system properties to gnu.classpath.*,
Jeroen Frijters <=
RE: Moving system properties to gnu.classpath.*, Jeroen Frijters, 2004/10/12
RE: Moving system properties to gnu.classpath.*, Jeroen Frijters, 2004/10/12
RE: Moving system properties to gnu.classpath.*, Jeroen Frijters, 2004/10/13