On Wed, Sep 09, 2009 at 09:24:12PM +0200, Marcus Better wrote:
> the file /etc/inint.d/tomcat6 should be left alone, the security manager
> can be disabled in /etc/default/tomcat6.
Thanks. That was just my quick workaround.
> Apparently a security manager permission problem. The manager app seems
> to need
> permission java.util.PropertyPermission "catalina.base", "read";
>
> You can add the appropriate permissions in /etc/tomcat6/policy.d, but
> actually I have no idea how it could work on 6.0.20-2 if the rules were
> not there in the first place.
Well, that rule *is* there in the default installation. The problem
seems to be that something prevents it reading any policy files, and
*any* web applications from running!
We have a test application (on another server) with
grant codeBase "file:/usr/share/masterkey/torus/-" {
permission java.security.AllPermission;
};
but our application crashes with the same error message. I just reported
the admin thing, because that is installed directly from Debian, and
ought to work straight out of the box. I believe the problem is with
the tomcat package itself.
I suspect there is something fishy with file permissions and/or the way
the policy.d is concatenated into a single policy file (that seems to
be Debian-specific), but I haven't been able to debug it further.
--
Heikki Levanto heikki at indexdata dot dk "In Murphy We Turst"
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
