DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36086>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36086 Summary: FixCRLF by Admin-User messes up the ACL (Access Control List) on Windows for restricted-user Product: Ant Version: 1.6.1 Platform: Other OS/Version: Windows 2000 Status: NEW Severity: normal Priority: P2 Component: Core tasks AssignedTo: dev@ant.apache.org ReportedBy: [EMAIL PROTECTED] (I am using Ant 1.6.1 on Windows 2000 Professional) Applying FixCRLF to a file by an admin-user on windows makes the file not-accessible to restristed-user. My tests reveal that the ACL gets messed up somehow so that the file that we previously accessible to restricted-user becomes unaccessible to restricted-user if fixCRLF results in file being modified. Here is how Cygwin displays the file permissions before and after the fixCRLF operation: Original File: -rwx------+ 1 Administ None 78906 Jul 18 07:52 file.txt After fixCRLF by admin (as seen by restricted-user) ---------- 1 ???????? ???????? 78907 Aug 8 16:03 file.txt All the permissions are gone for the restricted user. The restricted user can no longer view/edit/copy/rename this file. The funny thing is that the restricted-user can delete this file successfully (However, there is no undo for this operation). I found Bug 34764 (Zip task sets '000' permission on UNIX) and Bug 23414 (using zip task on windows makes shell script unusable in linux) that discussed something about filemode/dirmode. I am not sure, if any of this is related. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]