On Wed, 20 Feb 2002, Paul Speed wrote: > particular concern to paranoid sysadmins (redundant?). If I run > tomcat with a security manager I should be able to turn off native > code completely in the policy file. Then I only need to audit the > source code for the launcher to verify that my system is safe (within > the boundaries of my Java policy file). It's one of the nice things > about Java servers; a decent security model. Of course, it would be > nice if Catalina shipped with a better default security policy, but > that's a topic for another day. ;)
As I said, if you want port 80 you need root until you open the port. If you really want, you can write a small "RootLoader" that will just open 80 and chuid, and the connector use the opened Socket. And in policy specify only the RootLoader class as allowed to load native. Costin > > -Paul > > > > > To stop the whole kid, the destroy() method is called by the main thread > > after this receives a signal. The destroy method implementation will stop > > the thread in run(), clean all it has to clean, and return. > > > > When the thread going in run() returns, we simply call our exit() and > > terminate the JVM process.... > > > > IMO, this is the most portable thing, and design wise is kinda cool, as we > > "extend" the idea of a Runnable which is an object associated with a thread. > > A process is nothing else that a thread of execution associated with some > > memory, so, there's quite a nice parallel.... > > > > People might like it, people might not... Since I don't have time ATM , it's > > up to you folks... > > > > Pier > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
