Bug#412479: tomcat5.5: allow reads of catalina.base, catalina.home properties

Adrian Bridgett adrian at smop.co.uk
Mon Feb 26 10:43:54 UTC 2007


Package: tomcat5.5
Version: 5.5.20-4
Severity: minor

Now that the Java security manager is turned on by default (worth
highlighting in README.Debian?), I found that loggig was failing.

This was because I had a web-app logging to
${catalina.base}/logs/webappname.log

The application didn't have permission to read the catalina.base
property and so this failed (it tried to log to /logs/webappname.log).
(Tomcat logs using log4j were okay). 

Since many applications use this, I think it might be worth adding
permission to read these values:

// log4j and various other items want catalina.base
grant {
  permission java.util.PropertyPermission "catalina.base", "read";
  permission java.util.PropertyPermission "catalina.home", "read";
};


Adrian 
-- 
Adrian Bridgett - adrian at smop.co.uk
GPG key available on public key servers




More information about the pkg-java-maintainers mailing list