[
https://issues.apache.org/jira/browse/GERONIMO-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537227
]
David Jencks commented on GERONIMO-3451:
----------------------------------------
So addressing this issue will involve :
1. determine if the DefaultInstanceManager really needs to check for
restricted listeners
-- I invented this file for symmetry with the other restrictedXXX files.
Depending on what "really" means.... we need it as does tomcat.
2. if so, determine which listeners should be restricted (what to put in the
RestrictedListeners.properties)
There aren't any, tomcat didn't have this file or concept.
3. add RestrictedListeners.properties to Geronimo's catalina.jar
good idea.
4. fix the bug in DefaultInstanceManager mentioned above
very good idea.
I don't see how the bug can produce a problem right now since there aren't any
standard restricted listeners and anyone who can modify the restricted
listeners file could also modify the restricted filters file. On the other
hand I seem to be getting skilled at missing obvious security problems :-)
> "Restricted listeners property file not found" error logged during Tomcat
> server startup
> ----------------------------------------------------------------------------------------
>
> Key: GERONIMO-3451
> URL: https://issues.apache.org/jira/browse/GERONIMO-3451
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat
> Affects Versions: 2.0, 2.0.x
> Reporter: Kevan Miller
> Fix For: 2.0.x
>
>
> During Tomcat server startup, the following log error is displayed on the
> console:
> 12:57:32,559 ERROR [[/]] "Restricted listeners property file not found
> Althgough the log message can be ignored, users assume that something is
> broken...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
