View Issue Details

IDProjectCategoryView StatusLast Update
0003391Far ManagerCopy/Movepublic2017-01-28 23:18
ReporterpepakAssigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status newResolutionopen 
Platformx64OSWindowsOS Version7
Product Version3.0 
Target VersionFixed in Version 
Summary0003391: Move: Inherit Access Rights not inheriting correctly
DescriptionWhen performing a Move (F6) with access rights set to "Inherit", the access rights get copied (well, not exactly, see below) rather than inherited.
Steps To ReproduceSource files:
"." -> Everyone:RX (inherited from the parent directory, propagates to all sub-objects)
".\A.TXT" -> Everyone:RX (inherited from .)
".\B" -> Everyone:RX (inherited from .)
".\B\B.TXT" -> Everyone:RX (inherited from .\B)

Destination directory:
"T:\DEST" -> Everyone:F (explicit, propagates to all sub-objects)

Move ".\A.TXT" to "T:\DEST":
- Expected result: "T:\DEST\A.TXT" -> Everyone:F (inherited from T:\DEST)
- Actual result: "T:\DEST\A.TXT" -> Everyone:RX (inherited from ??? - surprisingly, there really is the "inherit" flag on the file!!)

Move ".\B" to "T:\DEST":
- Expected result: "T:\DEST\B\B.TXT" -> Everyone:F (inherited from T:\DEST\B, which itself inherits from T:\DEST)
- Actual result: "T:\DEST\B" -> Everyone:RX (inherited from ???)
- Actual result: "T:\DEST\B\B.TXT" -> Everyone:RX (inherited presumably from T:\DEST\B, but it could be inherited from ??? too)
Additional InformationCopy (F5) seems to work correctly with access rights set to "Inherit".

I suspect that in both cases, the setting is actually ignored and "Default" is used for access rights. At least, that's what the observed behavior indicates.

The bug is present since at least build 4797, possibly longer.
TagsNo tags attached.
Build

Relationships

duplicate of 0000987 new При move не обрабатывается случай inherit в копировании прав доступа. 

Activities

pepak

2017-01-28 19:55

reporter   bugnote:0015199

Interestingly enough, it seems to have started to work with a new instance of the FAR's process. So it would seem the error isn't simply "Inherit doesn't work", but instead "Something can make Inherit to be skipped during Copy/Move".

DrKnS

2017-01-28 23:16

administrator   bugnote:0015200

I presume you moved files to another volume in the first case, but not in the second?

It's known "feature" and default OS behaviour, see https://blogs.msdn.microsoft.com/oldnewthing/20060824-16

pepak

2017-01-28 23:18

reporter   bugnote:0015201

No. All the data were located on the T: drive.

Issue History

Date Modified Username Field Change
2017-01-28 13:54 pepak New Issue
2017-01-28 19:55 pepak Note Added: 0015199
2017-01-28 23:13 DrKnS Relationship added duplicate of 0000987
2017-01-28 23:16 DrKnS Note Added: 0015200
2017-01-28 23:18 pepak Note Added: 0015201