Writing to /Library/Application Support

Question

Created 1w

Replies 2

Boosts 0

Participants 2

I have seen these 2 articles that I have attached below that seem to offer some assistance. But is there a more modern way to share secured information between macOS users on same machine?

Entitlements

File System Protections

STEPS TO REPRODUCE

do
{
let baseDir = try fileMgr.url(for: .applicationSupportDirectory, in: .localDomainMask, appropriateFor: nil, create: true).appendingPathComponent("com.MyCompany.AppName", conformingTo: .directory)

try fileMgr.createDirectory(at: baseDir, withIntermediateDirectories: true, attributes: nil)
}
catch
{
Swift.print("ERROR: can't create baseDir \(baseDir)")
exit(0)
}

Boost

Answer 1

DTS Engineer OP

Apple

1w

Before continuing, read:

But is there a more modern way to share secured information between macOS users on same machine?

That depends on the nature of this information. What sort of information are you trying to share? And who are you trying to secure it from?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

VASoundman OP

2d

Thank you for your response.

The data we’re looking to share is application-specific configuration data that all users logged into the computer may need to access and read. The intent is for this data to be available to any user of the application across user sessions on the same device, without requiring duplication per-user. However, the data should remain protected from external modification by users who are not using our application (i.e., it should only be modified by our app).

We understand that LocalDomainMask can be used to create a directory in a location accessible to all users. However, this data is sensitive to the application’s functionality, so we’re looking for a secure and centralized storage location that enforces protections similar to those within a user’s Library directory but accessible by multiple users.

Is there a recommended entitlement or alternative approach for securely sharing such application-specific data between all users of a single computer?

Thank you for any insights into a modern, macOS-supported approach for this use case.

0