Note: This chapter describes property list keys specific to the macOS implementation of App Sandbox. They are not available in iOS.

Back in Mac OS X Lion, Apple took the decision to change the way saves work on Mac. Where once you'd find Save As, this was replaced by Duplicate which created versions of the same document. Mac will now ask you to confirm. That’s it, now you should be able to install or run any app no matter where it is downloaded from. To stay safer you can also choose ‘Mac App Store and identified developers’ option, which will only allow apps from developers approved by Apple.

In your macOS Xcode project, configure fine-grained security permissions by enabling settings in the Summary tab of the target editor. These settings, in turn, add Boolean values to entitlement keys in the target’s .entitlementsproperty list file. The values are then incorporated into the target’s code signature when you build the project.

You can think of using App Sandbox entitlements as a two-step process:

1. Sandbox a target, which removes most capabilities for interacting with the system

2. Restore capabilities to the sandboxed target, as needed, by configuring App Sandbox entitlements

At runtime, if a target requires a capability or a system resource for which the target isn’t entitled, the sandbox daemon (sandboxd) logs a violation message to the console.

For more information about App Sandbox, read App Sandbox Design Guide.

App Sandbox Entitlement Keys

This section describes the keys you can use to confer capabilities to a sandboxed app in macOS. The first key enables App Sandbox; the others configure the sandbox. If App Sandbox is not enabled, the other keys in this section are meaningless.

The value to use for any of these keys is a Boolean YES or NO, with the default value in each case being NO. If you are editing the .entitlements file directly in a text editor, the corresponding Boolean values to use are <true/> and <false/>. The default value for each key is false, so you can (and generally should) leave out the entitlement entirely rather than specifying a false value.

In cases where there are read-only and read/write entitlement key pairs, use of either key in the pair is mutually exclusive with the other.

Add these keys by using the Summary tab of the Xcode target editor. You can also add them directly to a target’s .entitlements file with the Xcode property list editor.

For information on additional entitlements for handling special circumstances, see App Sandbox Temporary Exception Entitlements.

For each key in this table, providing a Boolean value of YES enables the corresponding capability (unless otherwise noted).

Enables App Sandbox for a target in an Xcode project

Allows access to group containers that are shared among multiple apps produced by a single development team, and allows certain additional interprocess communication between the apps

Supported in macOS v10.7.5 and in v10.8.3 and later. The format for this attribute is described in Adding an App to an App Group.

Read-only access to the user’s Movies folder and iTunes movies

For details, see Enabling Access to Files in Standard Locations.

Read/write access to the user’s Movies folder and iTunes movies

For details, see Enabling Access to Files in Standard Locations.

Read-only access to the user’s Music folder

For details, see Enabling Access to Files in Standard Locations.

Read/write access to the user’s Music folder

For details, see Enabling Access to Files in Standard Locations.

Read-only access to the user’s Pictures folder

For details, see Enabling Access to Files in Standard Locations.

Read/write access to the user’s Pictures folder

For details, see Enabling Access to Files in Standard Locations.

Communication with AVB devices

For details, see Enabling Hardware Access.

Interaction with Bluetooth devices

For details, see Enabling Hardware Access.

Capture of movies and still images using the built-in camera, if available

For details, see Enabling Hardware Access.

Interaction with FireWire devices (currently, does not support interaction with audio/video devices such as DV cameras)

For details, see Enabling Hardware Access.

Recording of audio using the built-in microphone, if available, along with access to audio input using any Core Audio API that supports audio input

For details, see Enabling Hardware Access.

Interaction with serial devices

For details, see Enabling Hardware Access.

Interaction with USB devices, including HID devices such as joysticks

For details, see Enabling Hardware Access.

Read/write access to the user’s Downloads folder

For details, see Enabling Access to Files in Standard Locations.

Use of app-scoped bookmarks and URLs

For details, see Enabling Security-Scoped Bookmark and URL Access.

Use of document-scoped bookmarks and URLs

For details, see Enabling Security-Scoped Bookmark and URL Access.

Read-only access to files the user has selected using an Open or Save dialog

For details, see Enabling User-Selected File Access.

Read/write access to files the user has selected using an Open or Save dialog

For details, see Enabling User-Selected File Access.

Allows apps to write executable files.

For details, see Enabling User-Selected File Access.

Child process inheritance of the parent’s sandbox

For details, see Enabling App Sandbox Inheritance.

Network socket for connecting to other machines

For details, see Enabling Network Access.

Network socket for listening for incoming connections initiated by other machines

For details, see Enabling Network Access.

com.apple.security.personal-information.addressbook

Read/write access to contacts in the user’s address book; allows apps to infer the default address book if more than one is present on a system

For details, see Enabling Personal Information Access.

Read/write access to the user’s calendars

For details, see Enabling Personal Information Access.

Use of the Core Location framework for determining the computer’s geographical location

For details, see Enabling Personal Information Access.

Printing

For details, see Enabling Hardware Access.

Ability to use specific AppleScript scripting access groups within a specific scriptable app

For details, see Enabling Scripting of Other Apps.

Enabling App Sandbox

You enable App Sandbox individually for each target in an macOS Xcode project. For example, you may design a project as a main app, and some helpers in the form of XPC services. You then enable and configure the sandbox for each target individually.

To learn how to enable App Sandbox for your macOS app, which includes performing code signing, see App Sandbox Quick Start in App Sandbox Design Guide. The essential step is to ensure that the target editor checkbox named in Table 4-1 is selected.

Enabling User-Selected File Access

Xcode provides a pop-up menu, in the Summary tab of the target editor, with choices to enable read-only or read/write access to files and folders that the user explicitly selects. When you enable user-selected file access, you gain programmatic access to files and folders that the user opens using an NSOpenPanel object, and files the user saves using an NSSavePanel object.

Certain other user interactions, such as dragging items to your app or choosing items from the Open Recent menu, automatically expand your sandbox to include those items. Similarly, when macOS resumes an app after a reboot, the sandbox is automatically expanded to include any items that are automatically opened.

To enable user-selected file access in your app, use the Xcode target editor setting shown in Table 4-2.

Note: If your app needs to create executable files that are typically executed in some way other than through Launch Services (shell scripts, for example), you should also specify the com.apple.security.files.user-selected.executable entitlement.

By default, when writing executable files in sandboxed apps, the files are quarantined. Gatekeeper prevents quarantined executable files and other similar files (shell scripts, web archives, and so on) from opening or executing unless the user explicitly launches them from Finder.

If those executables are tools that are intended to run from the command line, such as shell scripts, this presents a problem. With this flag, the file quarantine system allows the app to write non-quarantined executables so that Gatekeeper does not prevent them from executing.

This entitlement does not have an Xcode checkbox, and thus must be added to your app’s entitlement property list manually. For details, see App Sandbox Entitlement Keys.

Enabling Access to Files in Standard Locations

In addition to granting user-selected file access, you can employ entitlements to grant programmatic file access to the following user folders:

• Downloads

• Music

• Movies

• Pictures

The Xcode control for enabling Downloads folder access is a checkbox; the controls for enabling access to these other folders are pop-up menus.

When you enable programmatic access to the user’s Movies folder, you also gain access to their iTunes movies.

Reopening of files by macOS using Resume does not require the presence of any entitlement key.

To enable programmatic access to specific folders, use the Xcode target editor settings shown in Table 4-3.

Enabling Security-Scoped Bookmark and URL Access

If you want to provide your sandboxed app with persistent access to file system resources, you must enable security-scoped bookmark and URL access. Security-scoped bookmarks are available starting in macOS v10.7.3.

To add the bookmarks.app-scope or bookmarks.document-scope entitlement, edit the target’s.entitlementsproperty list file using the Xcode property list editor. Use the entitlement keys shown in Table 4-4, depending on which type of access you want. Use a value of <true/> for each entitlement you want to enable. You can enable either or both entitlements.

For more information on security-scoped bookmarks, read Security-Scoped Bookmarks and Persistent Resource Access in App Sandbox Design Guide.

Enabling Network Access

Xcode’s Network checkboxes in the Summary tab of the target editor let you enable network access for your app.

To enable your app to connect to a server process running on another machine (or on the same machine), enable outgoing network connections.

To enable opening a network listening socket so that other computers can connect to your app, allow incoming network connections.

Note: Both outgoing and incoming connections can send and receive data. The sole difference is in whether your app is initiating the connection or is receiving connections initiated by other apps or other hosts.

To enable network access, use the Xcode target editor settings shown in Table 4-5.

Enabling Hardware Access

To allow a sandboxed target to access hardware services on a system—USB, printing, or the built-in camera and microphone—enable the corresponding setting in the Summary tab of the Xcode target editor.

• Camera access enables access to video and still image capture using the built-in camera, if available.

• Microphone access enables access to audio recording using the built-in microphone, if available.

• USB access enables the ability to interact with USB devices using USB device access APIs. On violation, sandboxd names the I/O Kit class your code tried to access.

• Printing access is required if you want to provide a target with the ability to print.

To enable access to hardware, use the Xcode target editor settings shown in Table 4-6.

To allow access to hardware devices for which no checkbox exists in Xcode’s user interface, you must manually add the appropriate entitlement to your app’s entitlements property list. These additional entitlements are listed in Table 4-7. All of these keys take a Boolean value.

Enabling Personal Information Access

A user’s personal information is inaccessible to your sandboxed app unless you grant access using the appropriate settings.

• Address Book access enables read/write access to contacts in the user’s address book.

• Location Services access enables use of the Core Location framework to determine the computer’s geographic position.

• Calendar access enables read/write access to the user’s calendars.

To enable access to personal information, use the Xcode target editor settings shown in Table 4-8.

Adding an App to an App Group

The com.apple.security.application-groups (available in macOS v10.7.5 and v10.8.3 and later) allows multiple apps produced by a single development team to share access to a special group container. This container is intended for content that is not user-facing, such as shared caches or databases.

In addition, this attribute allows the apps within the group to share Mach and POSIX semaphores and to use certain other IPC mechanisms among the group’s members. For additional details and naming conventions, read “Mach IPC and POSIX Semaphores and Shared Memory” in App Sandbox Design Guide.

The value for this key must be of type array, and must contain one or more string values, each of which must consist of your development team ID, followed by a period, followed by an arbitrary name chosen by your development team. For example:

The group containers are automatically created or added into each app’s sandbox container as determined by the existence of these keys. The group containers are stored in ~/Library/Group Containers/<application-group-id>, where <application-group-id> is one of the strings from the array. Your app can obtain the path to the group containers by calling the containerURLForSecurityApplicationGroupIdentifier: method of NSFileManager.

Enabling App Sandbox Inheritance

If your app employs a child process created with either the posix_spawn function or the NSTask class, you can configure the child process to inherit the sandbox of its parent. However, using a child process does not provide the security afforded by using an XPC service.

Important: XPC (as described in External Tools, XPC Services, and Privilege Separation) complements App Sandbox and is the preferred technology for implementing privilege separation in an macOS app. Before using a child process, consider using an XPC service instead.

To enable sandbox inheritance, a child target must use exactly two App Sandbox entitlement keys: com.apple.security.app-sandbox and com.apple.security.inherit. If you specify any other App Sandbox entitlement, the system aborts the child process. You can, however, confer other capabilities to a child process by way of iCloud and notification entitlements.

The main app in an Xcode project must never have a YES value for the inherit entitlement.

To add the inherit entitlement, edit the target’s .entitlementsproperty list file using the Xcode property list editor. Use the entitlement key shown in Table 4-9 with a value of <true/>.

Note: This property causes the child process to inherit only the static rights defined in the main app’s entitlements file, not any rights added to your sandbox after launch (such as PowerBox access to files).

If you need to provide access to files opened after launch, you must either pass the data to the helper or pass a bookmark to the child process. The bookmark need not be a security-scoped bookmark, but it can be, if desired.

If you are using other APIs to create child processes (such as NSWorkspace) and wish to have a shared container directory, you must use an app group.

Enabling Scripting of Other Apps

If your app needs to control another scriptable app, your app can use the scripting targets entitlement to request access to one or more of the scriptable app’s scripting access groups.

Note: Before you can use this entitlement, the scriptable app must provide scripting access groups. If it does not, you can still control the app, but you use a temporary exception entitlement instead. In some cases, you may use both scripting-targets entitlement and a temporary entitlement together, to provide support across different versions of the OS. For more information, see Apple Event Temporary Exception.

The scripting target entitlement contains a dictionary where each entry has the target app’s code signing identifier as the key, and an array of scripting access groups as the value. Scripting access groups are identified by strings and are specific to an app. For example, the following entry would grant access to composing mail messages with Apple’s Mail app:

For more information about how to add scripting access groups to an app, watch WWDC 2012: Secure Automation Techniques in OS X and read the manual page for sdef.

Copyright © 2017 Apple Inc. All Rights Reserved. Terms of Use | Privacy Policy | Updated: 2017-03-27

Apple started giving a security feature called System Integrity Protection with macOS X 10.11 El Capitan. It functions to prevent malware from modifying system files on your Mac. SIP is meant to protect your Mac from malicious software while running a user root account, and there should be no reason you’d like to disable it. But ultimately, if you want to gain access to some files, we have these quick steps ready for you to disable System Integrity Protection on Mac.

Cara Allow App Di Macromedia

What is System Integrity Protection on Mac?

• • Also known as “rootless mode”, System Integrity Protection blocks the route user from performing certain actions on the specific parts of the Mac operating system.
  • It won’t let potential malware software write access to protected files and folders on your Mac.
  • For macOS versions before EL Capitan, when SIP didn’t exist, root users could overwrite or modify any system file, folder, and application as there were no permission restrictions.
  • It will also prevent software from choosing a startup disk.

How to Turn OFF System Integrity Protection on Mac

1. Click on the Apple icon in the Menu bar of your Mac.
2. Select Restart.
3. Press and hold Command + R to reboot your Mac into Recovery Mode.
4. From available options, go into Utilities and then click on Terminal.
5. Type csrutil disableand press Return or Enter on your keyboard.
6. Close the Terminal menu.
7. At last, click on the Apple icon in the menu bar and select Restart.

And that’s it – System Integrity Protection on your Mac is disabled. You can enable it by following the same process except writing csrutil enable in the Terminal app.

Signing Off…

SIP is an extremely important and highly-secure security feature on Mac. During the time of raging cybercrime, you should always keep it enabled to safeguard and protect your Mac data from harmful and malicious software.

Check out these useful links related to the macOS and security of your iOS devices.

Cara Allow App Di Mac Os

The founder of iGeeksBlog, Dhvanesh, is an Apple aficionado, who cannot stand even a slight innuendo about Apple products. He dons the cap of editor-in-chief to make sure that articles match the quality standard before they are published.

• https://www.igeeksblog.com/author/dhvanesh/
• https://www.igeeksblog.com/author/dhvanesh/
• https://www.igeeksblog.com/author/dhvanesh/
• https://www.igeeksblog.com/author/dhvanesh/