[Solved] NTFS Permission inheritance after moving.

[h3ge]

I have an issue when moving files to my existing media library.
Downloaded files exist in Folder "Downloads" with Read/Write Permission to group "RES Data Download" also the extracted files will have that ntfs permission.

After I moved the files via FileBot the files itself doesn't get the permission from the destination folder (i.e. "RES Data Movie"), instead they still have the permission from the Download Folder. Newly created folders (during the moving) have the right permission, just not the files itself.
If I move the files by myself, the files get the new (right) permission.

Code: Select all

FileBot 4.7.5 (r4600)
JNA Native: 4.0.1
MediaInfo: 0.7.88
7-Zip-JBinding: 9.20
Chromaprint: 1.1.0
Extended Attributes: OK
Script Bundle: 2016-12-17 (r466)
Groovy: 2.4.7
JRE: Java(TM) SE Runtime Environment 1.8.0_60
JVM: 64-bit Java HotSpot(TM) 64-Bit Server VM
CPU/MEM: 16 Core / 839 MB Max Memory / 29 MB Used Memory
OS: Windows 10 (amd64)
Package: PORTABLE
Data: C:\XYZ\Programs\FileBot

Any idea how I can avoid this?

[rednoah]

FileBot is not aware of NTFS permissions in anyway. It doesn't read them before moving files and it doesn't set them after moving files.

On Unix systems you'd use umask to set the default permissions for new files. I don't know if there's a Windows / NTFS equivalent for setting default permissions.


EDIT:

Are you using the GUI or the CLI?

Thank you for your generous donation. Using the Windows Store version (you'll find a promo code in your inbox) may (or may not) make a difference.

[h3ge]

Thank you for your great work and for the promo code!

I'm using the GUI - with the Windows Store version it works! - Do you know the difference between the Store version and the portable version? - I would prefer if I can use the portable version.

Is there a way to change the move command? So I can use a custom powershell command.

[rednoah]

Setting -DuseNativeShell=true should do trick. You'll need the appropriate native libraries as well though if you set that option.

This will work for the portable GUI. I'm not sure if it'll have any effect on the portable CLI (probably not).

[h3ge]

Indeed, that did the trick! Thank you very much.