{"version":"2.1.282","anchor":"stricter-git-directory-tamper-checks-planted-symlinks-and-a","canonical_anchor":"stricter-git-directory-tamper-checks-planted-symlinks-and-a","heading":"Cloud folder sync checks more closely for a tampered git folder","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/stricter-git-directory-tamper-checks-planted-symlinks-and-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Cloud folder sync checks more closely for a tampered git folder\n\nFolder sync now looks for planted shortcuts in more parts of the git folder and treats a missing object store as a replaced one\n\n**Unclear.** It is not clear whether the earlier version already checked some of these locations in another way.\n\n**What**\n\nGit keeps its data in a hidden `.git` folder. The folder sync used with cloud sessions checks that this folder has not been altered to point somewhere else. That check is now stricter:\n\n- It looks for symbolic links in the parts of the folder that hold objects, branch and tag references, and related data. A symbolic link is a shortcut that points to another location.\n\n- This check now runs before the sync compares the folder's stored data.\n\n- A missing objects folder, which is where git keeps its data, now counts as replaced instead of being ignored.\n\n- When the objects folder has no `info` subfolder, the sync does not look inside it for pointers to other repositories.\n\n**Why**\n\nThese checks make it harder for a checked-out project to redirect the sync to another repository's data.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}