Sorry, of course, Bundle.loadClass makes sense this way.
Thanks for your answer on permission checks.
--
André
-Message d'origine-
De : Thomas Watson [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 18 janvier 2007 19:51
À : felix-dev@incubator.apache.org
Objet : RE: Code sharing and
"BOTTARO Andre RD-MAPS-GRE" <[EMAIL PROTECTED]> wrote on
01/18/2007 04:46:03 AM:
>
> This is a question asked by mobile operators moving from a
> constrained world (CLDC/MIDP) to a much more open one
> (CDC/OMEE/OSGi)... Code sharing is attractive if the system could
> guarantee the control o
bjet : Re: Code sharing and code isolation
That is a very wide question ...
I think you must reverse it, giving NO permissions to a bundle and
then adding permissions as needed. Dangerous things as having access
to the class loader or allowing Bundle.loadClass() are of course
dangerous.
However,
That is a very wide question ...
I think you must reverse it, giving NO permissions to a bundle and
then adding permissions as needed. Dangerous things as having access
to the class loader or allowing Bundle.loadClass() are of course
dangerous.
However, isn't it better to create a special permiss
BOTTARO Andre RD-MAPS-GRE wrote:
For security purposes, I would like to prevent bundles from using classes that belong to private packages of any bundle.
I checked that if I have a hacking bundle (B) with the following code, it will
be able to call a method (criticalAlert) on a private class
5 matches
Mail list logo