All geek questions in one place

File Security Attributes Dependent on File Copy

I have a windows service that updates our product. It copies the product files to a temporary directory, usually "C: \ Windows \ Temp", fixes the binaries, and then uses MoveFileEx to copy the files back to the installation directory on reboot, usually "C: \ Program Files \ Product". Files in the installation directory inherit their security attributes from the parent folder. After copying, repairing, and rebooting, files in the installation directory bypass some ACLs. In particular, files no longer have ACLs for the Users group, so users can no longer run the program after a reboot.

Can anyone explain what is going on here? It seems that copying from the installation directory to the temp directory files inherit access control lists from the temporary directory. However, in MoveFileEx / Reboot files only inherit ACLs that have both installation directories and temp.

+3
source share
2 answers

On Windows, if you copy a file, the file takes an ACL in the destination directory. If you move the file, the ACL goes with it, overriding everything that it can inherit from this directory. I'm not sure how MoveFileEx can work differently in a file.

temp (% TMP%, % TEMP% ), . , , , .

+4

- - , . . , , temp .

, , , , , .

0

Source: https://habr.com/ru/post/1698284/

More articles:


All Articles