Document the daemon socket restriction in the macOS MDM manifests

This commit is contained in:
Viktor Liu
2026-09-09 09:36:05 +02:00
parent 9a24fbe95f
commit 6f7e0409f8
2 changed files with 31 additions and 0 deletions
+15
View File
@@ -147,5 +147,20 @@
<string>com.acme.app1,com.acme.app2</string>
-->
<!-- ===== Daemon socket restriction =====
Restricts the daemon control socket, and the JSON socket where it is
enabled, to the listed principals. Accounts outside them cannot connect
at all. Overrides the install-time --allow-group in both directions; an
empty string lifts a restriction the install set.
Unix group IDs in gid:<id> form, comma-separated. Resolved IDs rather
than group names because the daemon reads this while starting and must
not wait on a directory service to resolve a name. A single group per
host: a Unix socket carries one owning group. -->
<!--
<key>allowGroups</key>
<string>gid:1001</string>
-->
</dict>
</plist>
+16
View File
@@ -165,6 +165,22 @@
<false/>
-->
<!-- ===== Daemon socket restriction =====
Restricts the daemon control socket, and the JSON socket
where it is enabled, to the listed principals. Accounts
outside them cannot connect at all. Overrides the
install-time --allow-group in both directions; an empty
string lifts a restriction the install set.
Unix group IDs in gid:<id> form, comma-separated. Resolved
IDs rather than group names because the daemon reads this
while starting and must not wait on a directory service.
One group per host: a Unix socket carries one owning group. -->
<!--
<key>allowGroups</key>
<string>gid:1001</string>
-->
</dict>
</dict>
</array>