App Translocation (Sierra & High Sierra)
Posted: Thu Oct 05, 2017 10:42 amI often fall foul to this security features. It requires apps be manually moved from wherever they have been downloaded in order to not be affected.
But I have Hazel move downloaded apps to /Applications
Could it be that Hazel could set whatever it needs to on moving an app to avoid Translocation?
Thanks
https://lapcatsoftware.com/articles/app ... ation.html
But I have Hazel move downloaded apps to /Applications
Could it be that Hazel could set whatever it needs to on moving an app to avoid Translocation?
Thanks
https://lapcatsoftware.com/articles/app ... ation.html
Starting in OS X v10.12, you can no longer provide external code or data alongside your code-signed app in a zip archive or unsigned disk image. An app distributed outside the Mac App Store runs from a randomized path when it is launched and so cannot access such external resources.
If using a disk image to ship an app, users should drag the app from the image to its desired installation location (usually /Applications) before launching it. This also applies to apps installed via ZIP or other archive formats or apps downloaded to the Downloads directory: ask the user to drag the app to /Applications and launch it from there.
This practice avoids an attack where a validly signed app launched from a disk image, ZIP archive, or ISO (CD/DVD) image can load malicious code or content from untrusted locations on the same image or archive. Starting with macOS Sierra, running a newly-downloaded app from a disk image, archive, or the Downloads directory will cause Gatekeeper to isolate that app at a unspecified read-only location in the filesystem. This will prevent the app from accessing code or content using relative paths.