Bug#461355: tomcat5.5: More restrictive JULI permissions break java.util.logging.

[Alexander Hvostov]

On Thursday 17 January 2008, Marcus Better wrote:
> Yes, see #460839 where we deal with this for the tomcat5.5-webapps.
>
> The stricter permissions are part of a tightened security policy. I
> think our options are:
> (i) Change JULI not to look for the logging.properties in those places
> unless specifically configured to do it,
> (ii) Give blanket permission for JULI to look up logging.properties
> files in all webapps (possibly circumventing the security fix),
> (iii) Leave as is and let users add the necessary permissions.

It could just catch the SecurityException while looking for 
logging.properties and pretend that the file doesn't exist, possibly 
after logging a message saying so.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20080118/a33f8e11/attachment.pgp