sandboxing audio applications
sandboxing audio applications
- Subject: sandboxing audio applications
- From: Rudy Richter <email@hidden>
- Date: Fri, 18 Jan 2013 12:21:06 -0500
We have a bunch of audio playback applications that use a variety of APIs that fall under CoreAudio.
for Core MIDI we can use
<key>com.apple.security.temporary-exception.mach-lookup.global-name</key>
<array>
<string>com.apple.midiserver</string>
</array>
for Audio Units we can use this in the short term, until AU authors get on board with sandboxing their audio units
<key>com.apple.security.temporary-exception.audio-unit-host</key>
<true/>
the problem we've run into is relating to Audio devices that have their own drivers and we don't gain access to be able to play/record audio. I have already filed a a radar against this as its a pretty serious problem for us currently. rdar://problem/12836341
the gist is, without specifically calling out each device's driver in our entitlements we can't talk to this pro level hardware and maintaining such a list of what devices our users might use is not really an acceptable solution for this problem.
any comments from the CoreAudio team?
-rudy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden