We are experiencing behavior on where our users are noticing permission changes on their ssh keys and changing ownership of various local git repositories stored on their devices. It was narrowed down to the execution of ReACL.exe possibly being the cause of this issue. Is this a known issue of the tool?
GIT/SSH files/keys do not support multi-user ownership
The default ReACL behavior is when target security principals are added to the same ACLs where the source security principals are (dual-ACL). It can be changed by using "Never - replace source security principals".
Important: doing so will effectively prevent any rollback possibilities of the migrated machine.
Alternatively, users working with GIT can manually fix permissions after the Cutover by removing source security principals from GIT files.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center