|
From: <php...@li...> - 2009-04-29 19:40:07
|
<3af...@ma...> <3af...@ma...> Message-ID: <1f90ee22edd1aad825827c88d44b88f8@localhost> X-Sender: and...@te... Received: from 161.148.54.70 [161.148.54.70] with HTTP/1.1 (POST); Wed, 29 Apr 2009 08:41:43 -0300 User-Agent: RoundCube Webmail/0.1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Hello, Despite being "possible" to manipulate the global web.xml file it should be avoided. The deployment must be feasible using application's web.xml (and sometimes, the context.xml also) into the war file. Maybe even using some clever tomcat manager html interface command. Or using Ant commands (then, one more dependency). Or security issues will rise ahead. I guess the right way is a correct edition of /etc/tomcat5.5/policy.d/04webapps.policy using the debconf tools. The web.xml is deployed already, but it is blocked, afaik. Suggestions are welcome. Regards. Andre Felipe Machado On Wed, 29 Apr 2009 21:03:07 +0200, php...@li... wrote: > Hi Andre, > > Is it possible to install the bridge so that the debian security manager > doesn't stop the back end from running php, if no apache is installed or > used? As described here: > http://php-java-bridge.sourceforge.net/pjb/FAQ.html#global-servlet > > If it is not possible to manipulate tomcat's global web.xml from a debian > package, we could leave it as it is and add a note to the debian install > instructions > so that users can change the web.xml themselves. > > Regards, > Jost Boekemeier |