Tell application "System Events" to get the name of every login item
#Bettertouchtool for mac sierra 10.12 code
For example, using System Events in code such as The privacy control system, TCC, lets this pass without any concerns over privacy, and it doesn’t trigger any dialogs.Īctions which are potentially more risky are handled with much greater care. Tell application "Finder" to reveal thePath Set thePath to POSIX file "/Users/me/Documents/myDoc.text" When an app calls an AppleEvent (or runs AppleScript) which performs an entirely innocent task, such as What I describe here may well have changed completely by Christmas, or maybe even sooner. What Mojave currently does for Automation is very likely to evolve over the coming days, weeks, and months. There is no system of whitelists or blacklists to distinguish between the effects of commands on your privacy. An app running a line of AppleScript could be using it to display a file’s location in a Finder window, running a command with elevated privileges, or stealing the contents of emails. The snag is that putting simple limits on the use of AppleEvents to control other apps can easily leave vulnerabilities.
This makes controls on Automation one of the most important features in Mojave’s new privacy system. So all a developer would have to do would be to locate features in an app which does have access to protected data (or services or hardware), and control that app using AppleEvents, to circumvent Mojave’s privacy. And some of the most surprising apps call the occasional snippet of AppleScript to enable important features. Many excellent apps are built largely on bringing together features of different apps using AppleEvents. But macOS has always had powerful means by which apps can control other apps – AppleEvents – which are exposed to the user in scripting systems, notably AppleScript, and Automator. Regulating direct access by apps to protected data is relatively simple, and should be highly effective. Yesterday, I looked at how Mojave’s new privacy protection works for data, services (Location) and hardware (camera and microphone), and largely ducked the most thorny issue of apps and scripts controlling other apps – Automation.
0 kommentar(er)
