You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shale.apache.org by "Craig McClanahan (JIRA)" <ji...@apache.org> on 2006/12/16 04:10:57 UTC
[jira] Resolved: (SHALE-344) Remoting does not provide configurable
limiting of exposed resources
[ http://issues.apache.org/struts/browse/SHALE-344?page=all ]
Craig McClanahan resolved SHALE-344.
------------------------------------
Fix Version/s: 1.0.4-SNAPSHOT
(was: TBD)
Resolution: Fixed
Tightened up default rules for the "dynamic" (map to method binding) processor, and made any user specified "excludes" list *add to* rather than replace the default excludes. With this, I'm declaring this to be fixed for 1.0.4.
> Remoting does not provide configurable limiting of exposed resources
> --------------------------------------------------------------------
>
> Key: SHALE-344
> URL: http://issues.apache.org/struts/browse/SHALE-344
> Project: Shale
> Issue Type: Bug
> Components: Remoting
> Reporter: Craig McClanahan
> Assigned To: Craig McClanahan
> Fix For: 1.0.4-SNAPSHOT
>
>
> Shale Remoting's current Processor implementations provide limited hard coded limitations on what resources may be accessed (cannot download classpath resources named "*.class", cannot download webapp resources named "/WEB-INF/*"), but they need to provide configurable settings for more fine grain control. In addition, reasonably secure defaults should be provided.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira