> > I need to implement, in principle for JServ 1.1, a SecurityManager which > essentially keeps all servlets of a given VM chrooted, in the sense that > these should ideally only be allowed to: > > - read files under certain canonical path > - write files under another canon. path > > I was going to investigate which SecurityManager implementation and setup > would be appropriate in order to allow JServ to work, and at the same time > providing at least part of the above protection. I'm thinking of adding a > configuration parameter of "securitymanager" or similar and, if set, > instantiating and setting the custom security manager at some place, maybe > after calling start() at org.apache.jserv.JServ. That won't work...imagine this case...someone could write a shell script that got executed by the Java code...now you are just locking down more than the file read/write classes/methods... You are opening up a can of worms with what you are trying to do. Your best bet is to have each user run their own VM in their own zone. That way, they can only destroy files they have unix privs to destroy. -jon -- ---------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html> Problems?: [EMAIL PROTECTED]
