DO NOT REPLY [Bug 22417] New: - add an "owner", "group", and "umask" to the task

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22417>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22417

add an "owner", "group", and "umask" to the <war> task

           Summary: add an "owner", "group", and "umask" to the <war> task
           Product: Ant
           Version: 1.5.3
          Platform: Other
               URL: http://ant.apache.org/manual/CoreTasks/war.html
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core
        AssignedTo: dev@ant.apache.org
        ReportedBy: hauser@acm.org


One use of this is for example when deploying to a tomcat webserver via the
"destfile" attribute (see http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22405).

The war file should only be owned e.g. by the user/group "tomcat" and have the
permission 7*0 (or as umask 00*7)

Obviously, an implementation of this would only be able to downgrade the rights,
i.e. if root (/sudo) is running the build.xml, user "tomcat" can be set.
If user "developer" with umask 0022 runs it, the user cannot be changed, but the
 permissions for example could be set to 750 or 644.

I suggest this for <war>, but obviously equal results can be achieved if it were
available for <copy> or <move>.

P.S.: See also the complementary RFE to just passively test whether the
environment is set up all right from a security perspective:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22370

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org