CamilleScholtz/swmpc / .agents/skills/audit-xcode-security-settings
audit-xcode-security-settings
VerifiedAudit and enable security-oriented Xcode build settings, compiler warnings, static analysis, and Enhanced Security features.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 57.4 KB |
| references/additional-settings.md | markdown | 1016 B |
| references/adoption-strategy.md | markdown | 5.6 KB |
| references/checked-pointer-arithmetic.md | markdown | 13.7 KB |
| references/cpp-hardening.md | markdown | 3.5 KB |
| references/decision-document.md | markdown | 3.3 KB |
| references/enhanced-security.md | markdown | 9.2 KB |
| references/hardware-memory-tagging.md | markdown | 4.1 KB |
| references/pointer-authentication.md | markdown | 6.8 KB |
| references/reading-build-settings.md | markdown | 5.7 KB |
| references/readonly-platform-memory.md | markdown | 2.5 KB |
| references/runtime-restrictions.md | markdown | 2.8 KB |
| references/security-compiler-warnings.md | markdown | 3.2 KB |
| references/security-settings-reference.md | markdown | 10.5 KB |
| references/stack-zero-init.md | markdown | 1.9 KB |
| references/typed-allocators.md | markdown | 3.2 KB |
| references/universal-binaries-for-libraries.md | markdown | 6.1 KB |
| scripts/filter_build_settings.pyexecutable | script | 3.9 KB |
references/readonly-platform-memory.md
View on GitHub# Read-Only Platform Memory
Marks regions of memory used by the platform for internal state (such as the dynamic loader) as read-only, preventing tampering.
> **Apple developer documentation:** entitlement reference for [`com.apple.security.hardened-process.dyld-ro`](doc://com.apple.documentation/documentation/BundleResources/Entitlements/com.apple.security.hardened-process.dyld-ro).
## What It Does
Informs the system to mark memory regions in your process that the platform uses for its internal state as **read-only**. This primarily protects the dynamic loader (dyld) internal data structures from being modified by an attacker who has achieved code execution in your process.
## What Vulnerabilities It Mitigates
- **Dyld state tampering** — an attacker modifying the dynamic loader's internal data to redirect library loading
- **Runtime metadata corruption** — overwriting platform-internal data structures to alter program behavior
- **Post-exploitation persistence** — modifying loader state to maintain control after initial exploitation
## How to Enable
**Xcode UI:** Signing & Capabilities > Enhanced Security > check "Enable Read-Only Platform Memory"
**Entitlement:** `com.apple.security.hardened-process.dyld-ro`
Enabled by default when you add the Enhanced Security capability.
## Code Changes Required
**Usually none.** In most applications, this entitlement requires no code changes.
The only exception: if your app **modifies data in protected memory regions** (for example, modifying the value of `const` data sections), the system will crash your app. Fix: remove the code that writes to read-only memory.
## How to Disable
**Xcode UI:** Uncheck "Enable Read-Only Platform Memory" in the Enhanced Security capability
## Platform Availability
- iOS, iPadOS, macOS, visionOS
- Available on all supported hardware
## Performance and Stability Impact
- **Performance:** None. Memory is marked read-only at load time; no ongoing runtime checks.
- **Stability:** Unless your code writes to `const` data sections or platform-internal memory (which is already a bug), this has zero impact.
## Why This Feature Is Low-Risk
Read-only platform memory is one of the safest Enhanced Security features:
- No runtime cost
- No code changes for well-behaved code
- Only crashes code that was already doing something wrong (writing to `const` memory)
- Provides meaningful protection against post-exploitation techniques
Enable this early alongside compiler warnings and stack zero init.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |