Post

Replies

Boosts

Views

Activity

Reply to Supported pre-initializer capture and failure enforcement for macOS guests
Apologies—the “DRAFT, NOT SENT” line was an internal preparation label accidentally left in the published post. The question is intended for discussion with Apple DTS. Could you first confirm whether supported public APIs can stop an unchanged Apple-signed tool inside a macOS guest after dyld bootstrap but before any initializer or other target code, capture its actual loaded images and bytes coherently, and keep it blocked or terminate it before forbidden instructions if the observer fails or disappears? The original requirements remain unchanged, including protection against compromised guest root and the submitting host’s administrator. If such a supported interface exists, which host/guest macOS versions, symbols and entitlements are required? If it does not, which interface or guarantee is missing?
Topic: App & System Services SubTopic: Core OS Tags:
2w
Reply to Supported pre-initializer capture and failure enforcement for macOS guests
Apologies—the “DRAFT, NOT SENT” line was an internal preparation label accidentally left in the published post. The question is intended for discussion with Apple DTS. Could you first confirm whether supported public APIs can stop an unchanged Apple-signed tool inside a macOS guest after dyld bootstrap but before any initializer or other target code, capture its actual loaded images and bytes coherently, and keep it blocked or terminate it before forbidden instructions if the observer fails or disappears? The original requirements remain unchanged, including protection against compromised guest root and the submitting host’s administrator. If such a supported interface exists, which host/guest macOS versions, symbols and entitlements are required? If it does not, which interface or guarantee is missing?
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
2w