Community
Participate
Working Groups
When a file is copied from system A to system B, permission bits are not copied, unless both systems support TAR archives and "supertransfer" is activated. In order to support permission bits for such copy, either - APIs need to be added to read / set permission bits and other extended attributes (does not seem practical), or - APIs need to be added to support supertransfer through archives in a more transparent manner. I think the best solution would be that - Each system type registers the kinds of supertransfer that it supports - During Copy, a "handshake" is done between source and target in order to come up with a common kind of supertransfer that both support - If a common supertransfer is found, permissions can be retained. This proposal is covered in bug 165890.
We found problems with trying to preserve too many permissions (ACLs, Ownership) on Windows Vista, so we decided to not have RSE play he administrator game for now -- admins will likely prefer a commandline anyways. See bug 181667 comment 7 for details. Some file properties like "Read Only", "Modification Time", should be preserved though. This could work great through EFS if generic properties were supported as suggested by bug 176051: the intersection of the properties supported for reading by the source filesystem and the properties supported for writing by the target file system should be copied.