On Saturday 03 April 2004 18:22, Nader Aeinehchi wrote: > In many systems I have looked at, a kernel typically starts several > containers which in turn may start other containers/applications.
Merlin's Kernel is pretty limited, and not really worth adding any security features, since the same can basically be done by the java.security.policy file. The interesting parts lies in the possibility to assign grants to 'components' instead of codebases, as they may share the codebase, i.e. permissions for the same codebase is given depending how it is 'mounted' in the application hierarchy. That is what we are trying to solve now. Next step is to make a facility which provides the JAAS style subject level security. I have a rough cut on how that would work in my head, but nothing written down. Niclas -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
