[TxMt] Re: osascript sandboxing under mojave?

[Allan Odgaard]

On 1 Jul 2018, at 2:56, Ronald Wampler wrote:

> I’m not running Mojave yet, but have you tried adding the apps under 
> “Application Data” too?

Also not on Mojave but I read this blog post: 
https://www.felix-schwarz.org/blog/2018/06/apple-event-sandboxing-in-macos-mojave

It points to these shortcomings (direct quotes):

1. Even if trusting an app targeting a large (or even open-ended) list 
of other apps, users can't whitelist it to avoid constantly running into 
auth prompts.

2. Authorization can't be re-requested. F.ex. in response to a click on 
an "Authorize" button in an alert stating that the app lacks a 
permission.

I take that to mean that there is (currently) no way for the user to say 
that TextMate is allowed to send AppleEvents to any app on the system, 
and if the user (accidentally) clicks something other than 
“Authorize” the first time that TextMate sends an AppleEvent to e.g. 
R.app, there is no way for TextMate to bring up this dialog again, and 
probably no way for the user to manually add R.app as one of the apps 
TextMate is allowed to send AppleEvents to.

Maybe `tccutil` can be used to reset the list of “denied” 
applications. Try `man tccutil` in Mojave and see if anything is written 
about AppleEvents.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macromates.com/textmate/attachments/20180701/b9869e62/attachment.html>