rename project to runaway

This commit is contained in:
2026-11-09 10:13:51 +08:00
parent 5857081832
commit c9feb8c05a
95 changed files with 1034 additions and 1034 deletions
+2 -2
View File
@@ -1,6 +1,6 @@
title: unleash
title: runaway
description: Single-script MDM bypass for macOS — covers all 5 layers of Apple MDM enrollment
url: "https://unleash-nine.vercel.app"
url: "https://runaway-nine.vercel.app"
baseurl: ""
theme: jekyll-theme-cayman
markdown: kramdown
+3 -3
View File
@@ -19,7 +19,7 @@
<a id="skip-to-content" href="#content">Skip to the content.</a>
<nav class="nav" role="navigation" aria-label="Documentation navigation">
<a href="/" class="logo" data-pt="/pt/">unleash</a>
<a href="/" class="logo" data-pt="/pt/">runaway</a>
<div id="search-wrap">
<input type="text" id="search-input" placeholder="Search docs..." autocomplete="off">
@@ -41,8 +41,8 @@
<a href="/security" data-pt="/pt/security">Security</a>
<h3>External</h3>
<a href="https://github.com/mateussiqueira/unleash" target="_blank">GitHub</a>
<a href="https://github.com/mateussiqueira/unleash/blob/main/CHANGELOG.md" target="_blank">Changelog</a>
<a href="https://github.com/mateussiqueira/runaway" target="_blank">GitHub</a>
<a href="https://github.com/mateussiqueira/runaway/blob/main/CHANGELOG.md" target="_blank">Changelog</a>
</nav>
<header class="page-header" role="banner">
+48 -48
View File
@@ -1,6 +1,6 @@
---
layout: default
title: Commands Reference — unleash
title: Commands Reference — runaway
---
# Commands Reference
@@ -19,34 +19,34 @@ title: Commands Reference — unleash
Creates a temporary admin account and suppresses all 5 layers of MDM.
**Must run from Recovery.**
```bash
./unleash bypass
./runaway bypass
```
### `suppress`
Silences MDM enrollment without creating a new user.
Works from both Recovery and booted systems.
```bash
sudo ./unleash suppress
sudo ./runaway suppress
```
### `heal`
Re-applies suppression after macOS updates re-enable enrollment daemons.
On booted systems, needs sudo. With `persist`, runs automatically on each boot.
```bash
sudo ./unleash heal
sudo ./runaway heal
```
### `persist`
Installs a LaunchDaemon that runs `heal` automatically on every boot.
Survives macOS updates.
```bash
sudo ./unleash persist
sudo ./runaway persist
```
### `unpersist`
Removes the persistence LaunchDaemon.
```bash
sudo ./unleash unpersist
sudo ./runaway unpersist
```
---
@@ -64,20 +64,20 @@ Kernel-level packet filtering. Blocks Apple's entire IP range (`17.0.0.0/8`).
DoH-proof — cannot be bypassed by DNS-over-HTTPS.
**Warning:** Breaks iCloud, App Store, and system updates.
```bash
sudo ./unleash firewall
sudo ./runaway firewall
```
### `firewall-off`
Removes pf firewall rules added by `firewall`.
```bash
sudo ./unleash firewall-off
sudo ./runaway firewall-off
```
### `whitelist`
Resolves only MDM domains to IPs and blocks those specifically.
Keeps iCloud and App Store working while blocking MDM enrollment.
```bash
sudo ./unleash whitelist
sudo ./runaway whitelist
```
---
@@ -93,7 +93,7 @@ sudo ./unleash whitelist
Kills running MDM processes, removes configuration profiles, and flushes DNS cache.
Useful when MDM is actively enrolling on a booted system.
```bash
sudo ./unleash harden
sudo ./runaway harden
```
### `audit`
@@ -104,7 +104,7 @@ Performs a deep MDM scan:
- Searches for MDM certificates
- Generates a risk score (0–100)
```bash
sudo ./unleash audit
sudo ./runaway audit
```
---
@@ -126,7 +126,7 @@ sudo ./unleash audit
Returns **SAFE TO FORMAT** (no MDM) or **MDM DETECTED** (will lock after wipe).
Also checks upgrade safety for macOS updates.
```bash
sudo ./unleash check
sudo ./runaway check
```
### `monitor`
@@ -134,14 +134,14 @@ Background daemon that checks MDM state every 5 minutes.
Sends a macOS notification if MDM tries to re-enroll.
Supports optional `--webhook` for Discord alerts.
```bash
sudo ./unleash monitor
sudo ./unleash monitor --webhook https://discord.com/api/webhooks/...
sudo ./runaway monitor
sudo ./runaway monitor --webhook https://discord.com/api/webhooks/...
```
### `history`
Shows the event log from previous monitor and heal runs.
```bash
sudo ./unleash history
sudo ./runaway history
```
---
@@ -155,21 +155,21 @@ sudo ./unleash history
| `dualboot` | Target an external macOS install |
### `backup`
Saves `/etc/hosts`, MDM profile state, launchd disabled overrides, and Unleash config.
Saves `/etc/hosts`, MDM profile state, launchd disabled overrides, and Runaway config.
```bash
sudo ./unleash backup
sudo ./runaway backup
```
### `restore`
Reverts the system to a previously saved state.
```bash
sudo ./unleash restore
sudo ./runaway restore
```
### `dualboot`
Creates an admin account and applies suppression to an external/bootcamp volume.
```bash
sudo ./unleash dualboot
sudo ./runaway dualboot
```
---
@@ -188,35 +188,35 @@ sudo ./unleash dualboot
Interactive wizard that runs the full setup:
firewall → monitor → persist → backup → audit.
```bash
sudo ./unleash init
sudo ./runaway init
```
### `suggest`
Analyzes your system and provides risk-based recommendations.
```bash
sudo ./unleash suggest
sudo ./runaway suggest
```
### `remediate`
Per-org MDM cleanup. Supports: JAMF, Mosyle, Addigy, Kandji, VMware.
Auto-detects the org from your DEP record.
```bash
sudo ./unleash remediate
sudo ./runaway remediate
```
### `predict`
Reads the serial number prefix and checks against known MDM org prefixes.
Useful before buying a used Mac.
```bash
./unleash predict ABC12345678
./runaway predict ABC12345678
```
### `telemetry`
Manages anonymous usage stats (opt-in, OFF by default).
```bash
./unleash telemetry on
./unleash telemetry off
./unleash telemetry status
./runaway telemetry on
./runaway telemetry off
./runaway telemetry status
```
---
@@ -232,9 +232,9 @@ Manages anonymous usage stats (opt-in, OFF by default).
Designed for org-provided Macs that must enroll but should only communicate while on VPN.
Blocks MDM IPs when the device is NOT connected to your VPN tunnel.
```bash
sudo ./unleash vpn-kill
sudo ./unleash vpn-kill-status
sudo ./unleash vpn-kill-remove
sudo ./runaway vpn-kill
sudo ./runaway vpn-kill-status
sudo ./runaway vpn-kill-remove
```
---
@@ -254,40 +254,40 @@ sudo ./unleash vpn-kill-remove
### `update`
Downloads the latest release from GitHub. GPG-verifies the signature.
```bash
sudo ./unleash update
sudo ./runaway update
```
### `uninstall`
Removes all Unleash traces. Prompts for confirmation.
Removes all Runaway traces. Prompts for confirmation.
```bash
sudo ./unleash uninstall
sudo ./runaway uninstall
```
### `reinstall`
Uninstalls then re-applies persist + whitelist + monitor.
```bash
sudo ./unleash reinstall
sudo ./runaway reinstall
```
### `config`
View or edit persistent settings in `~/.unleash.conf`.
View or edit persistent settings in `~/.runaway.conf`.
```bash
./unleash config
./unleash config show
./unleash config set key value
./runaway config
./runaway config show
./runaway config set key value
```
### `report`
Generates a full status report. Supports `--json` for machine-readable output.
```bash
sudo ./unleash report
sudo ./unleash report --json
sudo ./runaway report
sudo ./runaway report --json
```
### `demo`
Runs a simulated bypass flow. No real changes are made.
```bash
./unleash demo
./runaway demo
```
---
@@ -302,9 +302,9 @@ Runs a simulated bypass flow. No real changes are made.
Sends Discord DMs when MDM activity is detected.
```bash
sudo ./unleash discord-bot <token> <userId>
sudo ./unleash discord-bot-status
sudo ./unleash discord-bot-stop
sudo ./runaway discord-bot <token> <userId>
sudo ./runaway discord-bot-status
sudo ./runaway discord-bot-stop
```
---
@@ -321,22 +321,22 @@ sudo ./unleash discord-bot-stop
Checks: root privileges, Recovery mode detection, bash version,
disk/volume availability required libraries, and internet connectivity.
```bash
./unleash doctor
./runaway doctor
```
### `status`
Shows DEP marker state, hosts file, daemon overrides.
Only works from Recovery. Use `check` or `audit` on booted systems.
```bash
./unleash status
./unleash status -d
./runaway status
./runaway status -d
```
### `test`
Dry-run mode. Simulates a command without making real changes.
```bash
./unleash test bypass
./unleash test all
./runaway test bypass
./runaway test all
```
---
+7 -7
View File
@@ -1,10 +1,10 @@
## unleash v2.0.0 — Terminal Demo
## runaway v2.0.0 — Terminal Demo
```
$ sudo ./unleash --version
unleash v1.6.0
$ sudo ./runaway --version
runaway v1.6.0
$ sudo ./unleash check
$ sudo ./runaway check
[DRY-RUN] System Assessment
✓ Recovery mode: yes
✓ Data volume: /Volumes/Data (123.4 GB free)
@@ -13,7 +13,7 @@ $ sudo ./unleash check
⚠ Previous bypass: detected
VP>: SAFE TO FORMAT (no active MDM record)
$ sudo ./unleash audit
$ sudo ./runaway audit
[AUDIT] Deep MDM Scan
Active profiles: 0
DEP enrollment: clean
@@ -21,14 +21,14 @@ $ sudo ./unleash audit
Daemon overrides: 4/4 active
Risk score: 0 (LOW)
$ sudo ./unleash status -d
$ sudo ./runaway status -d
[ OK] System: clean
[ OK] Profiles: 0
[INF] MDM: no enrollment found
[INF] User artifacts: none
[ OK] Last check: 30s ago
$ sudo ./unleash report --json
$ sudo ./runaway report --json
{
"version": "1.6.0",
"platform": "darwin",
+7 -7
View File
@@ -4,13 +4,13 @@
<circle cx="18" cy="16" r="6" fill="#f38ba8"/>
<circle cx="36" cy="16" r="6" fill="#fab387"/>
<circle cx="54" cy="16" r="6" fill="#a6e3a1"/>
<text x="360" y="22" fill="#6c7086" text-anchor="middle" font-size="12">unleash — terminal demo</text>
<text x="360" y="22" fill="#6c7086" text-anchor="middle" font-size="12">runaway — terminal demo</text>
<text x="16" y="60" fill="#89b4fa" xml:space="preserve">$ sudo ./unleash --version</text>
<text x="16" y="80" fill="#cdd6f4" xml:space="preserve">unleash v1.6.0</text>
<text x="16" y="100" fill="#89b4fa" xml:space="preserve">$ sudo ./unleash doctor</text>
<text x="16" y="60" fill="#89b4fa" xml:space="preserve">$ sudo ./runaway --version</text>
<text x="16" y="80" fill="#cdd6f4" xml:space="preserve">runaway v1.6.0</text>
<text x="16" y="100" fill="#89b4fa" xml:space="preserve">$ sudo ./runaway doctor</text>
<text x="16" y="118" fill="#a6e3a1">✓</text>
<text x="32" y="118" fill="#cdd6f4">Script location: /Users/user/unleash</text>
<text x="32" y="118" fill="#cdd6f4">Script location: /Users/user/runaway</text>
<text x="16" y="134" fill="#a6e3a1">✓</text>
<text x="32" y="134" fill="#cdd6f4">Library files: 22/22 modules loaded</text>
<text x="16" y="150" fill="#a6e3a1">✓</text>
@@ -19,7 +19,7 @@
<text x="32" y="166" fill="#cdd6f4">Recovery mode: no (limited to booted commands)</text>
<text x="16" y="182" fill="#a6e3a1">✓</text>
<text x="32" y="182" fill="#cdd6f4">pfctl available</text>
<text x="16" y="202" fill="#89b4fa" xml:space="preserve">$ sudo ./unleash check</text>
<text x="16" y="202" fill="#89b4fa" xml:space="preserve">$ sudo ./runaway check</text>
<text x="16" y="220" fill="#a6e3a1">✓</text>
<text x="32" y="220" fill="#cdd6f4">Recovery mode: yes</text>
<text x="16" y="236" fill="#a6e3a1">✓</text>
@@ -29,7 +29,7 @@
<text x="16" y="268" fill="#a6e3a1">✓</text>
<text x="32" y="268" fill="#cdd6f4">MDM domains blocked: 13/13</text>
<text x="16" y="288" fill="#cba6f7" font-weight="bold" xml:space="preserve">VP>: SAFE TO FORMAT — no active MDM record</text>
<text x="16" y="312" fill="#89b4fa" xml:space="preserve">$ sudo ./unleash report --json</text>
<text x="16" y="312" fill="#89b4fa" xml:space="preserve">$ sudo ./runaway report --json</text>
<text x="16" y="330" fill="#cdd6f4">{</text>
<text x="16" y="346" fill="#cdd6f4"> "version": "1.6.0", "arch": "arm64",</text>
<text x="16" y="362" fill="#cdd6f4"> "mdm_enrolled": false, "risk_score": 0</text>

Before

Width:  |  Height:  |  Size: 2.4 KiB

After

Width:  |  Height:  |  Size: 2.4 KiB

+15 -15
View File
@@ -1,6 +1,6 @@
---
layout: default
title: FAQ — unleash
title: FAQ — runaway
---
# FAQ
@@ -13,7 +13,7 @@ title: FAQ — unleash
### Is this the same as bypass-mdm?
No. The original bypass-mdm scripts (v2, v3, express) only handle DEP markers and `/etc/hosts`. Unleash covers all five layers:
No. The original bypass-mdm scripts (v2, v3, express) only handle DEP markers and `/etc/hosts`. Runaway covers all five layers:
- DEP markers (same as original)
- Network blocking via `/etc/hosts` (same)
@@ -38,7 +38,7 @@ No. Clean install wipes the Data volume. Re-run `bypass` from Recovery after rei
### Will this survive a macOS update?
Usually yes, with `persist`. The LaunchDaemon runs `heal` automatically on the next boot after an update. Without `persist`, run `sudo ./unleash heal` manually.
Usually yes, with `persist`. The LaunchDaemon runs `heal` automatically on the next boot after an update. Without `persist`, run `sudo ./runaway heal` manually.
### Can the organization track this?
@@ -50,13 +50,13 @@ Yes. Use `whitelist` instead of `firewall` or the basic `suppress`. It resolves
### Why does MDM come back after Migration Assistant?
Migration Assistant copies user-level caches, preferences, and launch agents from the old Mac. These contain MDM enrollment artifacts that re-trigger the enrollment process. Most tools only clean system-level DEP markers — Unleash also cleans every user's Library directory.
Migration Assistant copies user-level caches, preferences, and launch agents from the old Mac. These contain MDM enrollment artifacts that re-trigger the enrollment process. Most tools only clean system-level DEP markers — Runaway also cleans every user's Library directory.
### Is there a GUI?
Not yet. The CLI is the primary interface. A SwiftUI wrapper is on the [roadmap](https://github.com/mateussiqueira/unleash/blob/main/ROADMAP.md).
Not yet. The CLI is the primary interface. A SwiftUI wrapper is on the [roadmap](https://github.com/mateussiqueira/runaway/blob/main/ROADMAP.md).
### How is unleash licensed?
### How is runaway licensed?
MIT. Free to use, modify, and distribute.
@@ -65,7 +65,7 @@ MIT. Free to use, modify, and distribute.
### How do I know if my Mac is enrolled in MDM?
```bash
sudo ./unleash check
sudo ./runaway check
```
Returns SAFE TO FORMAT (no MDM) or MDM DETECTED (will lock after wipe).
@@ -73,14 +73,14 @@ Returns SAFE TO FORMAT (no MDM) or MDM DETECTED (will lock after wipe).
### How do I check if the bypass is still working?
```bash
sudo ./unleash status -d
sudo ./runaway status -d
```
Checks DEP markers, hosts file, daemon overrides, and profile enrollment state.
### `profiles status -v` still shows an MDM profile — why?
Cosmetic. macOS stores the profile enrollment state on the read-only System Sealed Volume. The actual enrollment daemons are disabled and the DEP markers are gone. Trust `unleash status` over `profiles status`.
Cosmetic. macOS stores the profile enrollment state on the read-only System Sealed Volume. The actual enrollment daemons are disabled and the DEP markers are gone. Trust `runaway status` over `profiles status`.
### What's the difference between `monitor` and `persist`?
@@ -104,12 +104,12 @@ It reads the serial number prefix and checks it against known MDM org prefixes (
Run from Recovery:
```bash
sudo ./unleash suppress
sudo ./runaway suppress
```
Or from a booted system:
```bash
sudo ./unleash harden
sudo ./runaway harden
```
### "Not a known DirStatus" error
@@ -118,7 +118,7 @@ Volume auto-detection failed. Find your Data volume:
```bash
diskutil list
diskutil mount /dev/diskXsY
./unleash bypass
./runaway bypass
```
### FileVault unlock fails in Recovery
@@ -127,13 +127,13 @@ You need a user password or the FileVault recovery key. If neither is available,
### "Not a macOS Data volume"
Unleash checks for `/private/var/db/dslocal/nodes/Default` on the mounted volume. If it's missing, you mounted the wrong disk. Run `diskutil list` to find the correct Data volume.
Runaway checks for `/private/var/db/dslocal/nodes/Default` on the mounted volume. If it's missing, you mounted the wrong disk. Run `diskutil list` to find the correct Data volume.
### Monitor won't start
1. Check if it's already running: `sudo ./unleash monitor-status`
1. Check if it's already running: `sudo ./runaway monitor-status`
2. Check permissions: needs root
3. Check logs: `/var/log/unleash-monitor.log`
3. Check logs: `/var/log/runaway-monitor.log`
---
+11 -11
View File
@@ -1,20 +1,20 @@
---
layout: default
title: Architecture Guide — unleash
title: Architecture Guide — runaway
---
# Architecture Guide
## The Five Layers of MDM
Apple's MDM enrollment works through five independent mechanisms. Blocking just one or two is why bypass tools fail over time. Unleash addresses all five.
Apple's MDM enrollment works through five independent mechanisms. Blocking just one or two is why bypass tools fail over time. Runaway addresses all five.
```
Layer 1: DEP markers ─── /var/db/ConfigurationProfiles/Settings/.cloudConfig*
Layer 2: Hosts block ─── /etc/hosts → 0.0.0.0 deviceenrollment.apple.com
Layer 3: Daemons ─── launchd disabled → ManagedClient.enroll, activationd
Layer 4: User data ─── ~/Library/Preferences/com.apple.mdm.*
Layer 5: pf firewall ─── pf anchor com.unleash/mdm → kernel-level drop
Layer 5: pf firewall ─── pf anchor com.runaway/mdm → kernel-level drop
```
### Layer 1: DEP Enrollment Markers
@@ -100,8 +100,8 @@ pf (packet filter) operates at the kernel networking layer, below DNS resolution
## Script Architecture
```
unleash/
├── unleash # Main entry point — loads libs, dispatches commands
runaway/
├── runaway # Main entry point — loads libs, dispatches commands
├── lib/
│ ├── colors.sh # Logging, colors, prompts, show_cmd_help()
│ ├── detect.sh # Recovery detection, volume mounting
@@ -138,28 +138,28 @@ unleash/
### Dispatch Flow
1. `unleash` loads all `lib/*.sh` modules
2. `load_config()` reads `~/.unleash.conf` (if exists)
1. `runaway` loads all `lib/*.sh` modules
2. `load_config()` reads `~/.runaway.conf` (if exists)
3. Command argument is matched against the `case` dispatch in main
4. Handler function is called (e.g., `cmd_bypass`, `cmd_firewall`)
5. Each handler calls lib functions that do the actual work
### Standalone Build
`examples/build-standalone.sh` concatenates all lib modules + main script body into a single file (`unleash-standalone.sh`, ~3200 lines). No external dependencies — runs on any macOS system with bash.
`examples/build-standalone.sh` concatenates all lib modules + main script body into a single file (`runaway-standalone.sh`, ~3200 lines). No external dependencies — runs on any macOS system with bash.
## Build Process
1. **Source**: Individual `lib/*.sh` modules + `unleash` entry point
1. **Source**: Individual `lib/*.sh` modules + `runaway` entry point
2. **Test**: 78 Bats tests covering all modules
3. **Build**: `bash examples/build-standalone.sh` → `unleash-standalone.sh`
3. **Build**: `bash examples/build-standalone.sh` → `runaway-standalone.sh`
4. **Sign**: `scripts/sign-release.sh` → GPG detached signature
5. **Release**: GitHub release with standalone + signature + checksums
## Security Design
### No root persistence
Unleash does not install a backdoor, create hidden users, or modify the system volume. All changes are reversible.
Runaway does not install a backdoor, create hidden users, or modify the system volume. All changes are reversible.
### GPG-signed releases
Releases are signed with a GPG key. `selfupdate` verifies the signature before applying updates. Signature verification must pass or the update is rejected.
+1 -1
View File
@@ -28,5 +28,5 @@
fill="none" stroke="#a6e3a1" stroke-width="20" stroke-linecap="round" stroke-linejoin="round"/>
<!-- Text -->
<text x="256" y="492" fill="#6c7086" font-family="SFMono-Regular,Consolas,monospace" font-size="28" text-anchor="middle" font-weight="bold" letter-spacing="4">UNLEASH</text>
<text x="256" y="492" fill="#6c7086" font-family="SFMono-Regular,Consolas,monospace" font-size="28" text-anchor="middle" font-weight="bold" letter-spacing="4">RUNAWAY</text>
</svg>

Before

Width:  |  Height:  |  Size: 1.4 KiB

After

Width:  |  Height:  |  Size: 1.4 KiB

+49 -49
View File
@@ -1,13 +1,13 @@
---
layout: default
title: unleash
title: runaway
description: Single-script MDM bypass for macOS — covers all 5 layers of Apple MDM enrollment
---
<p align="center">
<img src="icon.svg" width="100" alt="unleash logo">
<img src="icon.svg" width="100" alt="runaway logo">
<br>
<strong>unleash</strong>
<strong>runaway</strong>
<br>
<em>Single-script MDM bypass for macOS</em>
</p>
@@ -23,12 +23,12 @@ description: Single-script MDM bypass for macOS — covers all 5 layers of Apple
---
unleash replaces the original five bypass-mdm scripts with a single file that handles every layer of Apple's MDM enrollment: DEP markers, network blocking, daemon overrides, user-level artifacts, and kernel-level firewall. Works from Recovery mode on Apple Silicon and Intel.
runaway replaces the original five bypass-mdm scripts with a single file that handles every layer of Apple's MDM enrollment: DEP markers, network blocking, daemon overrides, user-level artifacts, and kernel-level firewall. Works from Recovery mode on Apple Silicon and Intel.
**What makes unleash different from other bypass tools:**
**What makes runaway different from other bypass tools:**
- **Covers all 5 layers** — not just DEP markers or hosts file. Kills every path MDM uses to re-enroll.
- **User-level artifact cleanup** — Migration Assistant copies MDM caches per user. Unleash cleans every home directory.
- **User-level artifact cleanup** — Migration Assistant copies MDM caches per user. Runaway cleans every home directory.
- **Kernel-level pf firewall** — `/etc/hosts` is bypassed by DNS-over-HTTPS. pf is not.
- **Auto-heal daemon** — survives macOS updates. `persist` + `heal` catches whatever the update resets.
- **39 commands** — bypass, suppress, monitor, harden, audit, backup, predict, remediate, and more.
@@ -40,19 +40,19 @@ unleash replaces the original five bypass-mdm scripts with a single file that ha
**Homebrew (easiest)**
```bash
brew install mateussiqueira/unleash/unleash
brew install mateussiqueira/runaway/runaway
```
**Direct download**
```bash
curl -L https://raw.githubusercontent.com/mateussiqueira/unleash/main/unleash-standalone.sh -o unleash
chmod +x unleash
curl -L https://raw.githubusercontent.com/mateussiqueira/runaway/main/runaway-standalone.sh -o runaway
chmod +x runaway
```
**From a USB drive (for Recovery mode)**
1. Format a USB/SSD as FAT32, APFS, or exFAT
2. Copy the `unleash` folder (or just `unleash-standalone.sh`) to the drive
3. Boot to Recovery and run from `/Volumes/YourDrive/unleash`
2. Copy the `runaway` folder (or just `runaway-standalone.sh`) to the drive
3. Boot to Recovery and run from `/Volumes/YourDrive/runaway`
---
@@ -68,7 +68,7 @@ chmod +x unleash
3. Run:
```bash
"/Volumes/YourDrive/unleash" bypass
"/Volumes/YourDrive/runaway" bypass
```
4. Follow the prompts to create a temporary admin user
@@ -80,19 +80,19 @@ chmod +x unleash
If you already have a Mac that was previously bypassed and MDM came back after an update:
```bash
sudo ./unleash heal
sudo ./runaway heal
```
Or to check your current status:
```bash
sudo ./unleash status -d
sudo ./runaway status -d
```
### One-command setup (new Mac)
```bash
sudo ./unleash init
sudo ./runaway init
```
Interactive wizard that runs the full setup: firewall, monitor, persist, backup, and audit.
@@ -156,7 +156,7 @@ Interactive wizard that runs the full setup: firewall, monitor, persist, backup,
| `update` | Self-update from the latest GitHub release (GPG-verified) |
| `uninstall` | Complete removal with safety prompts |
| `reinstall` | Uninstall + install (atomic update) |
| `config` | View or edit persistent settings in `~/.unleash.conf` |
| `config` | View or edit persistent settings in `~/.runaway.conf` |
| `backup` | Save current state for later restore |
| `restore` | Restore from a previous backup |
| `demo` | Simulated bypass flow — no real changes |
@@ -205,8 +205,8 @@ dbs = discord-bot-stop dbs2 = discord-bot-status
### Before buying a used Mac
```bash
./unleash predict ABC12345678 # check serial against known org prefixes
./unleash check # is this Mac safe to wipe?
./runaway predict ABC12345678 # check serial against known org prefixes
./runaway check # is this Mac safe to wipe?
```
`predict` looks up the device serial against known MDM org prefixes. If it matches JAMF, Mosyle, or another org, you know what you're dealing with before you buy.
@@ -217,14 +217,14 @@ dbs = discord-bot-stop dbs2 = discord-bot-status
2. Migration Assistant copies your old data
3. MDM appears within minutes of login
**Fix**: Boot to Recovery and run `unleash suppress` (or `bypass` if you need a new admin user). This removes the DEP markers, user-level artifacts, and MDM preferences that MA transferred over.
**Fix**: Boot to Recovery and run `runaway suppress` (or `bypass` if you need a new admin user). This removes the DEP markers, user-level artifacts, and MDM preferences that MA transferred over.
### macOS update brought MDM back
1. System update restores enrollment daemons automatically
2. MDM block in `/etc/hosts` is often preserved
**Fix**: `sudo ./unleash heal` — re-disables daemons and re-checks all layers. If you ran `persist` before the update, this happens automatically on the next boot.
**Fix**: `sudo ./runaway heal` — re-disables daemons and re-checks all layers. If you ran `persist` before the update, this happens automatically on the next boot.
### Buying a former office Mac
@@ -233,23 +233,23 @@ dbs = discord-bot-stop dbs2 = discord-bot-status
**Strategy**:
- Boot to Recovery without connecting to Wi-Fi
- Run `unleash bypass` before the device ever phones home
- Run `unleash persist` and `unleash whitelist` so it stays clean
- Run `runaway bypass` before the device ever phones home
- Run `runaway persist` and `runaway whitelist` so it stays clean
- The serial stays in ABM forever — but as long as the device never connects with full protections removed, it will not re-enroll
### Used Mac that already has a user logged in
```bash
sudo ./unleash audit # check current state
sudo ./unleash harden # kill MDM processes immediately
sudo ./unleash whitelist # block MDM while keeping iCloud
sudo ./unleash persist # survive future updates
sudo ./runaway audit # check current state
sudo ./runaway harden # kill MDM processes immediately
sudo ./runaway whitelist # block MDM while keeping iCloud
sudo ./runaway persist # survive future updates
```
### Setting up a new Mac before first boot
1. Boot to Recovery without Wi-Fi
2. Run `unleash init` — interactive wizard
2. Run `runaway init` — interactive wizard
3. It will: suppress MDM, install persist, install whitelist, run audit
4. Reboot, set up normally, MDM never bothers you
@@ -257,7 +257,7 @@ sudo ./unleash persist # survive future updates
## How It Works
MDM (Mobile Device Management) operates in five layers on macOS. Unleash blocks every layer:
MDM (Mobile Device Management) operates in five layers on macOS. Runaway blocks every layer:
**Layer 1: DEP enrollment markers** → `/etc/hosts` block → **Layer 2: Network blocking**
@@ -269,13 +269,13 @@ MDM (Mobile Device Management) operates in five layers on macOS. Unleash blocks
In `/var/db/ConfigurationProfiles/Settings/`, Apple stores `.cloudConfig*` files that flag the Mac as DEP-enrolled. Removing these is the standard bypass approach, but macOS can recreate them from cached data.
**What unleash does**: Removes all `.cloudConfig*` markers, creates decoy files that tell macOS the device was never enrolled, and prevents re-creation by also blocking the network layer.
**What runaway does**: Removes all `.cloudConfig*` markers, creates decoy files that tell macOS the device was never enrolled, and prevents re-creation by also blocking the network layer.
### Layer 2: Network blocking
The MDM enrollment process phones home to Apple's servers. Blocking these domains prevents the device from checking in.
**What unleash does**:
**What runaway does**:
- **`/etc/hosts`** (basic): Blocks 13+ Apple MDM domains including `deviceenrollment.apple.com`, `mdmenrollment.apple.com`, `iprofiles.apple.com`. Both IPv4 (0.0.0.0) and IPv6 (::) entries.
- **pf firewall** (advanced): Kernel-level packet filtering that blocks MDM IP ranges even when DoH is used.
@@ -309,7 +309,7 @@ macOS ships with enrollment daemons that trigger enrollment on boot:
| `com.apple.mdmclient.daemon.runatboot` | MDM client |
| `com.apple.activationd` | Device activation |
**What unleash does**: Creates launchd disabled overrides for all four, preventing them from starting. Also disables Spotlight shortcut for Remote Management.
**What runaway does**: Creates launchd disabled overrides for all four, preventing them from starting. Also disables Spotlight shortcut for Remote Management.
### Layer 4: User-level artifacts
@@ -322,7 +322,7 @@ Migration Assistant and login caches leave MDM enrollment data in home directori
~/Library/LaunchAgents/com.apple.mdm.*
```
**What unleash does**: Scans every user's Library directory and removes all MDM-related preferences, caches, and launch agents. This is the step most other tools miss.
**What runaway does**: Scans every user's Library directory and removes all MDM-related preferences, caches, and launch agents. This is the step most other tools miss.
### Layer 5: pf firewall (optional, advanced)
@@ -370,11 +370,11 @@ Should work on any version that uses the same MDM enrollment mechanism — which
The most likely cause is user-level artifacts. Run from Recovery:
```bash
sudo ./unleash suppress
sudo ./runaway suppress
```
Or from a booted system:
```bash
sudo ./unleash harden
sudo ./runaway harden
```
### "Not a known DirStatus" error
@@ -382,22 +382,22 @@ sudo ./unleash harden
The script auto-detects volume names, but if you have a non-standard setup:
1. Run `diskutil list` to find your Data volume
2. Mount it: `diskutil mount /dev/diskXsY`
3. Re-run unleash
3. Re-run runaway
### Profiles still shows enrollment
This is cosmetic. macOS stores profile state on the read-only SSV (System Sealed Volume). Check the actual DEP markers instead:
```bash
sudo ./unleash status -d
sudo ./runaway status -d
```
### FileVault is enabled
Unleash will detect FileVault and prompt for the recovery key or volume password. If automatic unlock fails, unlock the volume manually in Disk Utility first.
Runaway will detect FileVault and prompt for the recovery key or volume password. If automatic unlock fails, unlock the volume manually in Disk Utility first.
### macOS update re-enabled MDM
Run `sudo ./unleash heal` after any macOS update. If you used `persist` before the update, it does this automatically on next boot.
Run `sudo ./runaway heal` after any macOS update. If you used `persist` before the update, it does this automatically on next boot.
### Can I use iCloud after bypass?
@@ -416,7 +416,7 @@ You need a second Mac with Apple Configurator 2 (free), a USB-C cable, and the I
2. Connect the locked Mac via USB-C while holding power
3. In Configurator: right-click the DFU device → Advanced → Restore
4. Pick the IPSW file, wait 10–30 minutes
5. After restore, boot to Recovery without Wi-Fi and run `unleash bypass`
5. After restore, boot to Recovery without Wi-Fi and run `runaway bypass`
**This erases all data.** IPSW files at [ipsw.me](https://ipsw.me).
@@ -430,7 +430,7 @@ All commands log with timestamps and levels:
[INF] Data volume: /Volumes/Macintosh HD - Data
[ OK] Admin 'apple' created (UID 501)
[WRN] DEP activation record present
[ERR] Firewall needs sudo: sudo ./unleash firewall
[ERR] Firewall needs sudo: sudo ./runaway firewall
[STP] Locating Data volume by APFS role...
[DBG] Checking pfctl availability
```
@@ -451,14 +451,14 @@ Use `--verbose` for debug messages and `--log-file <path>` to write everything t
## Links
- [GitHub Repository](https://github.com/mateussiqueira/unleash)
- [Full README](https://github.com/mateussiqueira/unleash/blob/main/README.md)
- [GitHub Repository](https://github.com/mateussiqueira/runaway)
- [Full README](https://github.com/mateussiqueira/runaway/blob/main/README.md)
- [Architecture Guide](guide)
- [FAQ](faq)
- [Quick Reference (QUICKSTART.md)](https://github.com/mateussiqueira/unleash/blob/main/QUICKSTART.md)
- [Changelog](https://github.com/mateussiqueira/unleash/blob/main/CHANGELOG.md)
- [Contributing](https://github.com/mateussiqueira/unleash/blob/main/CONTRIBUTING.md)
- [Code of Conduct](https://github.com/mateussiqueira/unleash/blob/main/CODE_OF_CONDUCT.md)
- [Security Policy](https://github.com/mateussiqueira/unleash/blob/main/SECURITY.md)
- [Discussions](https://github.com/mateussiqueira/unleash/discussions)
- [Report a Bug](https://github.com/mateussiqueira/unleash/issues/new?template=bug_report.md)
- [Quick Reference (QUICKSTART.md)](https://github.com/mateussiqueira/runaway/blob/main/QUICKSTART.md)
- [Changelog](https://github.com/mateussiqueira/runaway/blob/main/CHANGELOG.md)
- [Contributing](https://github.com/mateussiqueira/runaway/blob/main/CONTRIBUTING.md)
- [Code of Conduct](https://github.com/mateussiqueira/runaway/blob/main/CODE_OF_CONDUCT.md)
- [Security Policy](https://github.com/mateussiqueira/runaway/blob/main/SECURITY.md)
- [Discussions](https://github.com/mateussiqueira/runaway/discussions)
- [Report a Bug](https://github.com/mateussiqueira/runaway/issues/new?template=bug_report.md)
+17 -17
View File
@@ -1,6 +1,6 @@
---
layout: default
title: Installation — unleash
title: Installation — runaway
---
# Installation
@@ -8,51 +8,51 @@ title: Installation — unleash
## Homebrew (easiest)
```bash
brew tap mateussiqueira/unleash
brew install unleash
brew tap mateussiqueira/runaway
brew install runaway
```
Or in one step:
```bash
brew install mateussiqueira/unleash/unleash
brew install mateussiqueira/runaway/runaway
```
## Direct download
```bash
curl -L https://raw.githubusercontent.com/mateussiqueira/unleash/main/unleash-standalone.sh -o unleash
chmod +x unleash
sudo ./unleash init
curl -L https://raw.githubusercontent.com/mateussiqueira/runaway/main/runaway-standalone.sh -o runaway
chmod +x runaway
sudo ./runaway init
```
## From a USB drive (for Recovery mode)
1. Format a USB/SSD as **FAT32**, **APFS**, or **exFAT**
2. Copy the `unleash` folder (or just `unleash-standalone.sh`) to the drive
3. Boot to Recovery and run from `/Volumes/YourDrive/unleash`
2. Copy the `runaway` folder (or just `runaway-standalone.sh`) to the drive
3. Boot to Recovery and run from `/Volumes/YourDrive/runaway`
## Via curl in Recovery (needs internet)
```bash
curl -L https://raw.githubusercontent.com/mateussiqueira/unleash/main/unleash -o /tmp/unleash
chmod +x /tmp/unleash && /tmp/unleash bypass
curl -L https://raw.githubusercontent.com/mateussiqueira/runaway/main/runaway -o /tmp/runaway
chmod +x /tmp/runaway && /tmp/runaway bypass
```
## Building from source
```bash
git clone https://github.com/mateussiqueira/unleash.git
cd unleash
git clone https://github.com/mateussiqueira/runaway.git
cd runaway
bash examples/build-standalone.sh
# Output: unleash-standalone.sh (~3200 lines)
# Output: runaway-standalone.sh (~3200 lines)
```
## Verifying the installation
```bash
./unleash version
# → unleash v2.0.0
./runaway version
# → runaway v2.0.0
./unleash doctor
./runaway doctor
# Runs pre-flight diagnostics
```
+2 -2
View File
@@ -18,10 +18,10 @@
<circle cx="78" cy="80" r="6" fill="#f38ba8"/>
<circle cx="96" cy="80" r="6" fill="#fab387"/>
<circle cx="114" cy="80" r="6" fill="#a6e3a1"/>
<text x="200" y="86" fill="#6c7086" text-anchor="middle" font-family="SFMono-Regular,Consolas,monospace" font-size="13">unleash</text>
<text x="200" y="86" fill="#6c7086" text-anchor="middle" font-family="SFMono-Regular,Consolas,monospace" font-size="13">runaway</text>
<!-- Terminal lines -->
<text x="76" y="136" fill="#89b4fa" font-family="SFMono-Regular,Consolas,monospace" font-size="14">$ ./unleash bypass</text>
<text x="76" y="136" fill="#89b4fa" font-family="SFMono-Regular,Consolas,monospace" font-size="14">$ ./runaway bypass</text>
<!-- Progress bar animation -->
<rect x="76" y="156" width="248" height="8" fill="#313244" rx="4"/>

Before

Width:  |  Height:  |  Size: 2.3 KiB

After

Width:  |  Height:  |  Size: 2.3 KiB

+48 -48
View File
@@ -1,6 +1,6 @@
---
layout: default
title: Referência de Comandos — unleash
title: Referência de Comandos — runaway
---
# Referência de Comandos
@@ -19,34 +19,34 @@ title: Referência de Comandos — unleash
Cria uma conta admin temporária e suprime todas as 5 camadas do MDM.
**Deve executar do Recovery.**
```bash
./unleash bypass
./runaway bypass
```
### `suppress`
Silencia o registro MDM sem criar um novo usuário.
Funciona tanto do Recovery quanto do sistema já iniciado.
```bash
sudo ./unleash suppress
sudo ./runaway suppress
```
### `heal`
Reaplica a supressão após atualizações do macOS reativarem os daemons de registro.
Em sistemas já iniciados, precisa de sudo. Com `persist`, executa automaticamente em cada inicialização.
```bash
sudo ./unleash heal
sudo ./runaway heal
```
### `persist`
Instala um LaunchDaemon que executa `heal` automaticamente em cada inicialização.
Sobrevive a atualizações do macOS.
```bash
sudo ./unleash persist
sudo ./runaway persist
```
### `unpersist`
Remove o LaunchDaemon de persistência.
```bash
sudo ./unleash unpersist
sudo ./runaway unpersist
```
---
@@ -64,20 +64,20 @@ Filtragem de pacotes a nível de kernel. Bloqueia toda a faixa de IP da Apple (`
À prova de DoH — não pode ser contornado por DNS-over-HTTPS.
**Aviso:** Quebra iCloud, App Store e atualizações do sistema.
```bash
sudo ./unleash firewall
sudo ./runaway firewall
```
### `firewall-off`
Remove as regras pf adicionadas por `firewall`.
```bash
sudo ./unleash firewall-off
sudo ./runaway firewall-off
```
### `whitelist`
Resolve apenas domínios MDM para IPs e bloqueia especificamente aqueles.
Mantém iCloud e App Store funcionando enquanto bloqueia o registro MDM.
```bash
sudo ./unleash whitelist
sudo ./runaway whitelist
```
---
@@ -93,7 +93,7 @@ sudo ./unleash whitelist
Mata processos MDM em execução, remove perfis de configuração e limpa o cache DNS.
Útil quando o MDM está registrando ativamente em um sistema já iniciado.
```bash
sudo ./unleash harden
sudo ./runaway harden
```
### `audit`
@@ -104,7 +104,7 @@ Executa uma varredura MDM profunda:
- Procura certificados MDM
- Gera um score de risco (0–100)
```bash
sudo ./unleash audit
sudo ./runaway audit
```
---
@@ -126,7 +126,7 @@ sudo ./unleash audit
Retorna **SAFE TO FORMAT** (sem MDM) ou **MDM DETECTED** (vai travar após limpar).
Também verifica segurança para atualizações do macOS.
```bash
sudo ./unleash check
sudo ./runaway check
```
### `monitor`
@@ -134,14 +134,14 @@ Daemon em segundo plano que verifica o estado do MDM a cada 5 minutos.
Envia uma notificação do macOS se o MDM tentar re-registrar.
Suporta `--webhook` opcional para alertas no Discord.
```bash
sudo ./unleash monitor
sudo ./unleash monitor --webhook https://discord.com/api/webhooks/...
sudo ./runaway monitor
sudo ./runaway monitor --webhook https://discord.com/api/webhooks/...
```
### `history`
Mostra o log de eventos de execuções anteriores do monitor e heal.
```bash
sudo ./unleash history
sudo ./runaway history
```
---
@@ -155,21 +155,21 @@ sudo ./unleash history
| `dualboot` | Mira uma instalação macOS externa |
### `backup`
Salva `/etc/hosts`, estado dos perfis MDM, overrides launchd desabilitados e config do Unleash.
Salva `/etc/hosts`, estado dos perfis MDM, overrides launchd desabilitados e config do Runaway.
```bash
sudo ./unleash backup
sudo ./runaway backup
```
### `restore`
Reverte o sistema para um estado salvo anteriormente.
```bash
sudo ./unleash restore
sudo ./runaway restore
```
### `dualboot`
Cria uma conta admin e aplica supressão em um volume externo/bootcamp.
```bash
sudo ./unleash dualboot
sudo ./runaway dualboot
```
---
@@ -188,35 +188,35 @@ sudo ./unleash dualboot
Assistente interativo que executa a configuração completa:
firewall → monitor → persist → backup → audit.
```bash
sudo ./unleash init
sudo ./runaway init
```
### `suggest`
Analisa seu sistema e fornece recomendações baseadas em risco.
```bash
sudo ./unleash suggest
sudo ./runaway suggest
```
### `remediate`
Limpeza MDM por organização. Suporta: JAMF, Mosyle, Addigy, Kandji, VMware.
Detecta automaticamente a organização a partir do registro DEP.
```bash
sudo ./unleash remediate
sudo ./runaway remediate
```
### `predict`
Lê o prefixo do número serial e verifica contra prefixos conhecidos de organizações MDM.
Útil antes de comprar um Mac usado.
```bash
./unleash predict ABC12345678
./runaway predict ABC12345678
```
### `telemetry`
Gerencia estatísticas anônimas de uso (opt-in, DESLIGADO por padrão).
```bash
./unleash telemetry on
./unleash telemetry off
./unleash telemetry status
./runaway telemetry on
./runaway telemetry off
./runaway telemetry status
```
---
@@ -232,9 +232,9 @@ Gerencia estatísticas anônimas de uso (opt-in, DESLIGADO por padrão).
Projetado para Macs fornecidos por organizações que precisam registrar mas só devem se comunicar enquanto na VPN.
Bloqueia IPs MDM quando o dispositivo NÃO está conectado ao túnel VPN.
```bash
sudo ./unleash vpn-kill
sudo ./unleash vpn-kill-status
sudo ./unleash vpn-kill-remove
sudo ./runaway vpn-kill
sudo ./runaway vpn-kill-status
sudo ./runaway vpn-kill-remove
```
---
@@ -254,40 +254,40 @@ sudo ./unleash vpn-kill-remove
### `update`
Baixa o último release do GitHub. Verifica a assinatura GPG.
```bash
sudo ./unleash update
sudo ./runaway update
```
### `uninstall`
Remove todos os vestígios do Unleash. Pede confirmação.
Remove todos os vestígios do Runaway. Pede confirmação.
```bash
sudo ./unleash uninstall
sudo ./runaway uninstall
```
### `reinstall`
Desinstala e então reaplica persist + whitelist + monitor.
```bash
sudo ./unleash reinstall
sudo ./runaway reinstall
```
### `config`
Ver ou editar configurações persistentes em `~/.unleash.conf`.
Ver ou editar configurações persistentes em `~/.runaway.conf`.
```bash
./unleash config
./unleash config show
./unleash config set key value
./runaway config
./runaway config show
./runaway config set key value
```
### `report`
Gera um relatório completo de status. Suporta `--json` para saída legível por máquina.
```bash
sudo ./unleash report
sudo ./unleash report --json
sudo ./runaway report
sudo ./runaway report --json
```
### `demo`
Executa um fluxo de bypass simulado. Nenhuma alteração real é feita.
```bash
./unleash demo
./runaway demo
```
---
@@ -302,9 +302,9 @@ Executa um fluxo de bypass simulado. Nenhuma alteração real é feita.
Envia DMs no Discord quando atividade MDM é detectada.
```bash
sudo ./unleash discord-bot <token> <userId>
sudo ./unleash discord-bot-status
sudo ./unleash discord-bot-stop
sudo ./runaway discord-bot <token> <userId>
sudo ./runaway discord-bot-status
sudo ./runaway discord-bot-stop
```
---
@@ -321,22 +321,22 @@ sudo ./unleash discord-bot-stop
Verifica: privilégios root, detecção do modo Recovery, versão do bash,
disco/volume, bibliotecas necessárias e conectividade com a internet.
```bash
./unleash doctor
./runaway doctor
```
### `status`
Mostra estado dos marcadores DEP, arquivo hosts, overrides de daemon.
Só funciona do Recovery. Use `check` ou `audit` em sistemas já iniciados.
```bash
./unleash status
./unleash status -d
./runaway status
./runaway status -d
```
### `test`
Modo dry-run. Simula um comando sem fazer alterações reais.
```bash
./unleash test bypass
./unleash test all
./runaway test bypass
./runaway test all
```
---
+14 -14
View File
@@ -1,6 +1,6 @@
---
layout: default
title: FAQ — unleash
title: FAQ — runaway
---
# FAQ
@@ -13,7 +13,7 @@ title: FAQ — unleash
### É a mesma coisa que bypass-mdm?
Não. Os scripts originais do bypass-mdm (v2, v3, express) só lidam com marcadores DEP e `/etc/hosts`. O Unleash cobre todas as cinco camadas:
Não. Os scripts originais do bypass-mdm (v2, v3, express) só lidam com marcadores DEP e `/etc/hosts`. O Runaway cobre todas as cinco camadas:
- Marcadores DEP (igual ao original)
- Bloqueio de rede via `/etc/hosts` (igual)
@@ -38,7 +38,7 @@ Não. A instalação limpa apaga o volume de Dados. Execute `bypass` do Recovery
### Sobrevive a uma atualização do macOS?
Geralmente sim, com `persist`. O LaunchDaemon executa `heal` automaticamente na próxima inicialização após uma atualização. Sem `persist`, execute `sudo ./unleash heal` manualmente.
Geralmente sim, com `persist`. O LaunchDaemon executa `heal` automaticamente na próxima inicialização após uma atualização. Sem `persist`, execute `sudo ./runaway heal` manualmente.
### A organização pode rastrear isso?
@@ -50,11 +50,11 @@ Sim. Use `whitelist` em vez de `firewall` ou `suppress` básico. Ele resolve ape
### Por que o MDM volta depois do Migration Assistant?
O Migration Assistant copia caches, preferências e launch agents do Mac antigo. Estes contêm artefatos de registro MDM que reativam o processo de registro. A maioria das ferramentas só limpa marcadores DEP de nível de sistema — o Unleash também limpa o diretório Library de cada usuário.
O Migration Assistant copia caches, preferências e launch agents do Mac antigo. Estes contêm artefatos de registro MDM que reativam o processo de registro. A maioria das ferramentas só limpa marcadores DEP de nível de sistema — o Runaway também limpa o diretório Library de cada usuário.
### Tem interface gráfica?
Ainda não. A CLI é a interface principal. Um wrapper SwiftUI está no [roadmap](https://github.com/mateussiqueira/unleash/blob/main/ROADMAP.md).
Ainda não. A CLI é a interface principal. Um wrapper SwiftUI está no [roadmap](https://github.com/mateussiqueira/runaway/blob/main/ROADMAP.md).
### Qual é a licença?
@@ -65,7 +65,7 @@ MIT. Gratuito para usar, modificar e distribuir.
### Como saber se meu Mac está registrado no MDM?
```bash
sudo ./unleash check
sudo ./runaway check
```
Retorna SAFE TO FORMAT (sem MDM) ou MDM DETECTED (vai travar após limpar).
@@ -73,14 +73,14 @@ Retorna SAFE TO FORMAT (sem MDM) ou MDM DETECTED (vai travar após limpar).
### Como verificar se o bypass ainda está funcionando?
```bash
sudo ./unleash status -d
sudo ./runaway status -d
```
Verifica marcadores DEP, arquivo hosts, overrides de daemon e estado dos perfis.
### `profiles status -v` ainda mostra um perfil MDM — por quê?
Cosmético. O macOS armazena o estado dos perfis no SSV (Volume Selado do Sistema) somente leitura. Os daemons de registro reais estão desabilitados e os marcadores DEP foram removidos. Confie em `unleash status` em vez de `profiles status`.
Cosmético. O macOS armazena o estado dos perfis no SSV (Volume Selado do Sistema) somente leitura. Os daemons de registro reais estão desabilitados e os marcadores DEP foram removidos. Confie em `runaway status` em vez de `profiles status`.
### Qual a diferença entre `monitor` e `persist`?
@@ -104,12 +104,12 @@ Ele lê o prefixo do número serial e verifica contra prefixos conhecidos de org
Execute do Recovery:
```bash
sudo ./unleash suppress
sudo ./runaway suppress
```
Ou de um sistema já iniciado:
```bash
sudo ./unleash harden
sudo ./runaway harden
```
### Erro "Not a known DirStatus"
@@ -118,7 +118,7 @@ A detecção automática de volume falhou. Encontre seu volume de Dados:
```bash
diskutil list
diskutil mount /dev/diskXsY
./unleash bypass
./runaway bypass
```
### Desbloqueio do FileVault falha no Recovery
@@ -127,13 +127,13 @@ Você precisa de uma senha de usuário ou da chave de recuperação do FileVault
### "Not a macOS Data volume"
O Unleash verifica `/private/var/db/dslocal/nodes/Default` no volume montado. Se estiver faltando, você montou o disco errado. Execute `diskutil list` para encontrar o volume de Dados correto.
O Runaway verifica `/private/var/db/dslocal/nodes/Default` no volume montado. Se estiver faltando, você montou o disco errado. Execute `diskutil list` para encontrar o volume de Dados correto.
### Monitor não inicia
1. Verifique se já está rodando: `sudo ./unleash monitor-status`
1. Verifique se já está rodando: `sudo ./runaway monitor-status`
2. Verifique permissões: precisa de root
3. Verifique logs: `/var/log/unleash-monitor.log`
3. Verifique logs: `/var/log/runaway-monitor.log`
---
+11 -11
View File
@@ -1,20 +1,20 @@
---
layout: default
title: Guia de Arquitetura — unleash
title: Guia de Arquitetura — runaway
---
# Guia de Arquitetura
## As Cinco Camadas do MDM
O registro MDM da Apple funciona através de cinco mecanismos independentes. Bloquear apenas um ou dois é o motivo pelo qual ferramentas de bypass falham com o tempo. O Unleash aborda todos os cinco.
O registro MDM da Apple funciona através de cinco mecanismos independentes. Bloquear apenas um ou dois é o motivo pelo qual ferramentas de bypass falham com o tempo. O Runaway aborda todos os cinco.
```
Camada 1: Marcadores DEP ─── /var/db/ConfigurationProfiles/Settings/.cloudConfig*
Camada 2: Bloqueio hosts ─── /etc/hosts → 0.0.0.0 deviceenrollment.apple.com
Camada 3: Daemons ─── launchd desabilitado → ManagedClient.enroll, activationd
Camada 4: Dados usuário ─── ~/Library/Preferences/com.apple.mdm.*
Camada 5: Firewall pf ─── pf anchor com.unleash/mdm → bloqueio kernel
Camada 5: Firewall pf ─── pf anchor com.runaway/mdm → bloqueio kernel
```
### Camada 1: Marcadores de Registro DEP
@@ -100,8 +100,8 @@ pf (packet filter) opera na camada de rede do kernel, abaixo da resolução DNS.
## Arquitetura do Script
```
unleash/
├── unleash # Ponto de entrada principal
runaway/
├── runaway # Ponto de entrada principal
├── lib/
│ ├── colors.sh # Logging, cores, prompts, show_cmd_help()
│ ├── detect.sh # Detecção de Recovery, montagem de volume
@@ -138,28 +138,28 @@ unleash/
### Fluxo de Dispatch
1. `unleash` carrega todos os módulos `lib/*.sh`
2. `load_config()` lê `~/.unleash.conf` (se existir)
1. `runaway` carrega todos os módulos `lib/*.sh`
2. `load_config()` lê `~/.runaway.conf` (se existir)
3. O argumento do comando é casado com o `case` dispatch no main
4. A função handler é chamada (ex.: `cmd_bypass`, `cmd_firewall`)
5. Cada handler chama funções lib que fazem o trabalho real
### Build Autocontido
`examples/build-standalone.sh` concatena todos os módulos lib + corpo do script principal em um único arquivo (`unleash-standalone.sh`, ~3200 linhas). Sem dependências externas — funciona em qualquer macOS com bash.
`examples/build-standalone.sh` concatena todos os módulos lib + corpo do script principal em um único arquivo (`runaway-standalone.sh`, ~3200 linhas). Sem dependências externas — funciona em qualquer macOS com bash.
## Processo de Build
1. **Fonte**: Módulos `lib/*.sh` individuais + ponto de entrada `unleash`
1. **Fonte**: Módulos `lib/*.sh` individuais + ponto de entrada `runaway`
2. **Teste**: 78 testes Bats cobrindo todos os módulos
3. **Build**: `bash examples/build-standalone.sh` → `unleash-standalone.sh`
3. **Build**: `bash examples/build-standalone.sh` → `runaway-standalone.sh`
4. **Assinar**: `scripts/sign-release.sh` → Assinatura GPG destacada
5. **Release**: Release GitHub com standalone + assinatura + checksums
## Design de Segurança
### Sem persistência root
O Unleash não instala backdoor, cria usuários ocultos ou modifica o volume do sistema. Todas as alterações são reversíveis.
O Runaway não instala backdoor, cria usuários ocultos ou modifica o volume do sistema. Todas as alterações são reversíveis.
### Releases assinados com GPG
Releases são assinados com chave GPG. O `selfupdate` verifica a assinatura antes de aplicar atualizações.
+43 -43
View File
@@ -1,15 +1,15 @@
---
layout: default
title: unleash
title: runaway
description: Bypass MDM em um único script para macOS — cobre todas as 5 camadas do MDM da Apple
---
<p align="center">
<img src="../icon.svg" width="100" alt="unleash logo">
<img src="../icon.svg" width="100" alt="runaway logo">
<br>
<strong>unleash</strong>
<strong>runaway</strong>
<br>
<em>unleash</em>
<em>runaway</em>
</p>
<p align="center">
@@ -23,12 +23,12 @@ description: Bypass MDM em um único script para macOS — cobre todas as 5 cama
---
unleash substitui os cinco scripts originais do bypass-mdm em um único arquivo que lida com todas as camadas do registro MDM da Apple: marcadores DEP, bloqueio de rede, substituição de daemons, artefatos de nível de usuário e firewall a nível de kernel. Funciona no modo Recovery em Apple Silicon e Intel.
runaway substitui os cinco scripts originais do bypass-mdm em um único arquivo que lida com todas as camadas do registro MDM da Apple: marcadores DEP, bloqueio de rede, substituição de daemons, artefatos de nível de usuário e firewall a nível de kernel. Funciona no modo Recovery em Apple Silicon e Intel.
**O que torna o unleash diferente de outras ferramentas de bypass:**
**O que torna o runaway diferente de outras ferramentas de bypass:**
- **Cobre todas as 5 camadas** — não apenas marcadores DEP ou arquivo hosts. Bloqueia todos os caminhos que o MDM usa para re-registrar.
- **Limpeza de artefatos de usuário** — o Migration Assistant copia caches MDM por usuário. O Unleash limpa todos os diretórios home.
- **Limpeza de artefatos de usuário** — o Migration Assistant copia caches MDM por usuário. O Runaway limpa todos os diretórios home.
- **Firewall pf a nível de kernel** — `/etc/hosts` é contornado por DNS-over-HTTPS. pf não.
- **Daemon de auto-recuperação** — sobrevive a atualizações do macOS. `persist` + `heal` pegam tudo que a atualização resetar.
- **39 comandos** — bypass, suppress, monitor, harden, audit, backup, predict, remediate e mais.
@@ -40,19 +40,19 @@ unleash substitui os cinco scripts originais do bypass-mdm em um único arquivo
**Homebrew (mais fácil)**
```bash
brew install mateussiqueira/unleash/unleash
brew install mateussiqueira/runaway/runaway
```
**Download direto**
```bash
curl -L https://raw.githubusercontent.com/mateussiqueira/unleash/main/unleash-standalone.sh -o unleash
chmod +x unleash
curl -L https://raw.githubusercontent.com/mateussiqueira/runaway/main/runaway-standalone.sh -o runaway
chmod +x runaway
```
**De um pendrive USB (para o modo Recovery)**
1. Formate um USB/SSD como FAT32, APFS ou exFAT
2. Copie a pasta `unleash` (ou apenas `unleash-standalone.sh`) para o drive
3. Inicialize no Recovery e execute de `/Volumes/SeuDrive/unleash`
2. Copie a pasta `runaway` (ou apenas `runaway-standalone.sh`) para o drive
3. Inicialize no Recovery e execute de `/Volumes/SeuDrive/runaway`
---
@@ -68,7 +68,7 @@ chmod +x unleash
3. Execute:
```bash
"/Volumes/SeuDrive/unleash" bypass
"/Volumes/SeuDrive/runaway" bypass
```
4. Siga as instruções para criar um usuário admin temporário
@@ -80,19 +80,19 @@ chmod +x unleash
Se você já tem um Mac que foi bypassado anteriormente e o MDM voltou após uma atualização:
```bash
sudo ./unleash heal
sudo ./runaway heal
```
Ou para verificar o status atual:
```bash
sudo ./unleash status -d
sudo ./runaway status -d
```
### Configuração com um comando (Mac novo)
```bash
sudo ./unleash init
sudo ./runaway init
```
Assistente interativo que executa a configuração completa: firewall, monitor, persist, backup e audit.
@@ -156,7 +156,7 @@ Assistente interativo que executa a configuração completa: firewall, monitor,
| `update` | Autoatualização a partir do GitHub Releases (verificada com GPG) |
| `uninstall` | Remoção completa com confirmações de segurança |
| `reinstall` | Desinstalar + instalar (atualização atômica) |
| `config` | Ver/editar configurações persistentes em `~/.unleash.conf` |
| `config` | Ver/editar configurações persistentes em `~/.runaway.conf` |
| `backup` | Salva o estado atual para restaurar depois |
| `restore` | Restaura a partir de um backup anterior |
| `demo` | Fluxo de bypass simulado — sem alterações reais |
@@ -205,8 +205,8 @@ dbs = discord-bot-stop dbs2 = discord-bot-status
### Antes de comprar um Mac usado
```bash
./unleash predict ABC12345678 # verifica serial contra organizações conhecidas
./unleash check # este Mac é seguro para formatar?
./runaway predict ABC12345678 # verifica serial contra organizações conhecidas
./runaway check # este Mac é seguro para formatar?
```
`predict` consulta o serial contra prefixos conhecidos de organizações MDM. Se corresponder a JAMF, Mosyle ou outra, você sabe o que esperar antes de comprar.
@@ -217,19 +217,19 @@ dbs = discord-bot-stop dbs2 = discord-bot-status
2. O Migration Assistant copia seus dados antigos
3. O MDM aparece em minutos após o login
**Solução**: Inicialize no Recovery e execute `unleash suppress` (ou `bypass` se precisar de um novo admin). Remove os marcadores DEP, artefatos de usuário e preferências MDM que o MA transferiu.
**Solução**: Inicialize no Recovery e execute `runaway suppress` (ou `bypass` se precisar de um novo admin). Remove os marcadores DEP, artefatos de usuário e preferências MDM que o MA transferiu.
### Atualização do macOS trouxe o MDM de volta
1. A atualização do sistema restaura os daemons de registro automaticamente
2. O bloqueio MDM em `/etc/hosts` geralmente é preservado
**Solução**: `sudo ./unleash heal` — re-desabilita daemons e verifica todas as camadas. Se você executou `persist` antes da atualização, isso acontece automaticamente na próxima inicialização.
**Solução**: `sudo ./runaway heal` — re-desabilita daemons e verifica todas as camadas. Se você executou `persist` antes da atualização, isso acontece automaticamente na próxima inicialização.
### Configurando um Mac novo antes do primeiro boot
1. Inicialize no Recovery sem Wi-Fi
2. Execute `unleash init` — assistente interativo
2. Execute `runaway init` — assistente interativo
3. Ele irá: suprimir MDM, instalar persist, instalar whitelist, executar audit
4. Reinicie, configure normalmente, o MDM nunca incomoda
@@ -237,7 +237,7 @@ dbs = discord-bot-stop dbs2 = discord-bot-status
## Como Funciona
O MDM (Mobile Device Management) opera em cinco camadas no macOS. O Unleash bloqueia todas elas:
O MDM (Mobile Device Management) opera em cinco camadas no macOS. O Runaway bloqueia todas elas:
**Camada 1: Marcadores DEP** → `/etc/hosts` → **Camada 2: Bloqueio de rede**
@@ -249,13 +249,13 @@ O MDM (Mobile Device Management) opera em cinco camadas no macOS. O Unleash bloq
Em `/var/db/ConfigurationProfiles/Settings/`, a Apple armazena arquivos `.cloudConfig*` que marcam o Mac como registrado no DEP. Removê-los é a abordagem padrão de bypass.
**O que o unleash faz**: Remove todos os marcadores `.cloudConfig*`, cria arquivos falsos que dizem ao macOS que o dispositivo nunca foi registrado e impede a recriação bloqueando também a camada de rede.
**O que o runaway faz**: Remove todos os marcadores `.cloudConfig*`, cria arquivos falsos que dizem ao macOS que o dispositivo nunca foi registrado e impede a recriação bloqueando também a camada de rede.
### Camada 2: Bloqueio de rede
O cliente de registro contata os servidores da Apple para baixar o perfil MDM. Sem acesso à rede, ele não pode completar o registro.
**O que o unleash faz**:
**O que o runaway faz**:
- **`/etc/hosts`** (básico): Bloqueia 13+ domínios Apple MDM incluindo `deviceenrollment.apple.com`, `mdmenrollment.apple.com`, `iprofiles.apple.com`. Entradas IPv4 (0.0.0.0) e IPv6 (::).
- **Firewall pf** (avançado): Filtragem de pacotes a nível de kernel que bloqueia faixas de IP Apple mesmo quando DoH é usado.
@@ -289,7 +289,7 @@ O macOS registra quatro daemons de registro que executam na inicialização:
| `com.apple.mdmclient.daemon.runatboot` | Cliente MDM |
| `com.apple.activationd` | Ativação do dispositivo |
**O que o unleash faz**: Cria overrides launchd desabilitados para todos os quatro, impedindo que iniciem.
**O que o runaway faz**: Cria overrides launchd desabilitados para todos os quatro, impedindo que iniciem.
### Camada 4: Limpeza de artefatos de usuário
@@ -303,7 +303,7 @@ O Migration Assistant e caches de login deixam dados de registro MDM nos diretó
~/Library/LaunchAgents/com.apple.mdm.*
```
**O que o unleash faz**: Varre todos os diretórios home no volume de Dados e remove todos os preferences, caches e launch agents relacionados ao MDM.
**O que o runaway faz**: Varre todos os diretórios home no volume de Dados e remove todos os preferences, caches e launch agents relacionados ao MDM.
### Camada 5: Firewall pf (opcional, avançado)
@@ -350,11 +350,11 @@ Deve funcionar em qualquer versão que use o mesmo mecanismo de registro MDM —
A causa mais provável são artefatos de nível de usuário. Execute do Recovery:
```bash
sudo ./unleash suppress
sudo ./runaway suppress
```
Ou de um sistema já iniciado:
```bash
sudo ./unleash harden
sudo ./runaway harden
```
### Erro "Not a known DirStatus"
@@ -362,22 +362,22 @@ sudo ./unleash harden
O script detecta volumes automaticamente, mas se você tiver uma configuração não padrão:
1. Execute `diskutil list` para encontrar seu volume de Dados
2. Monte: `diskutil mount /dev/diskXsY`
3. Execute unleash novamente
3. Execute runaway novamente
### Perfis ainda mostram registro
Isso é cosmético. O macOS armazena estado de perfis no SSV (Volume Selado do Sistema). Verifique os marcadores DEP reais:
```bash
sudo ./unleash status -d
sudo ./runaway status -d
```
### FileVault está ativado
O Unleash detecta FileVault e pede a chave de recuperação ou senha do volume. Se o desbloqueio automático falhar, desbloqueie o volume manualmente no Utilitário de Disco primeiro.
O Runaway detecta FileVault e pede a chave de recuperação ou senha do volume. Se o desbloqueio automático falhar, desbloqueie o volume manualmente no Utilitário de Disco primeiro.
### Atualização do macOS reativou o MDM
Execute `sudo ./unleash heal` após qualquer atualização do macOS. Se você usou `persist` antes da atualização, isso acontece automaticamente na próxima inicialização.
Execute `sudo ./runaway heal` após qualquer atualização do macOS. Se você usou `persist` antes da atualização, isso acontece automaticamente na próxima inicialização.
### Posso usar iCloud após o bypass?
@@ -396,7 +396,7 @@ Você precisa de um segundo Mac com Apple Configurator 2 (grátis), um cabo USB-
2. Conecte o Mac travado via USB-C enquanto segura o power
3. No Configurator: clique com direito no dispositivo DFU → Advanced → Restore
4. Escolha o arquivo IPSW, aguarde 10–30 minutos
5. Após restaurar, inicialize no Recovery sem Wi-Fi e execute `unleash bypass`
5. Após restaurar, inicialize no Recovery sem Wi-Fi e execute `runaway bypass`
**Isso apaga todos os dados.** Arquivos IPSW em [ipsw.me](https://ipsw.me).
@@ -410,7 +410,7 @@ Todos os comandos registram com timestamps e níveis:
[INF] Data volume: /Volumes/Macintosh HD - Data
[ OK] Admin 'apple' created (UID 501)
[WRN] DEP activation record present
[ERR] Firewall needs sudo: sudo ./unleash firewall
[ERR] Firewall needs sudo: sudo ./runaway firewall
[STP] Locating Data volume by APFS role...
[DBG] Checking pfctl availability
```
@@ -431,13 +431,13 @@ Use `--verbose` para mensagens de debug e `--log-file <caminho>` para escrever t
## Links
- [Repositório GitHub](https://github.com/mateussiqueira/unleash)
- [README completo](https://github.com/mateussiqueira/unleash/blob/main/README.md)
- [Repositório GitHub](https://github.com/mateussiqueira/runaway)
- [README completo](https://github.com/mateussiqueira/runaway/blob/main/README.md)
- [Guia de Arquitetura](guide)
- [FAQ](faq)
- [Changelog](https://github.com/mateussiqueira/unleash/blob/main/CHANGELOG.md)
- [Contribuindo](https://github.com/mateussiqueira/unleash/blob/main/CONTRIBUTING.md)
- [Código de Conduta](https://github.com/mateussiqueira/unleash/blob/main/CODE_OF_CONDUCT.md)
- [Política de Segurança](https://github.com/mateussiqueira/unleash/blob/main/SECURITY.md)
- [Discussões](https://github.com/mateussiqueira/unleash/discussions)
- [Reportar Bug](https://github.com/mateussiqueira/unleash/issues/new?template=bug_report.md)
- [Changelog](https://github.com/mateussiqueira/runaway/blob/main/CHANGELOG.md)
- [Contribuindo](https://github.com/mateussiqueira/runaway/blob/main/CONTRIBUTING.md)
- [Código de Conduta](https://github.com/mateussiqueira/runaway/blob/main/CODE_OF_CONDUCT.md)
- [Política de Segurança](https://github.com/mateussiqueira/runaway/blob/main/SECURITY.md)
- [Discussões](https://github.com/mateussiqueira/runaway/discussions)
- [Reportar Bug](https://github.com/mateussiqueira/runaway/issues/new?template=bug_report.md)
+17 -17
View File
@@ -1,6 +1,6 @@
---
layout: default
title: Instalação — unleash
title: Instalação — runaway
---
# Instalação
@@ -8,51 +8,51 @@ title: Instalação — unleash
## Homebrew (mais fácil)
```bash
brew tap mateussiqueira/unleash
brew install unleash
brew tap mateussiqueira/runaway
brew install runaway
```
Ou em um passo:
```bash
brew install mateussiqueira/unleash/unleash
brew install mateussiqueira/runaway/runaway
```
## Download direto
```bash
curl -L https://raw.githubusercontent.com/mateussiqueira/unleash/main/unleash-standalone.sh -o unleash
chmod +x unleash
sudo ./unleash init
curl -L https://raw.githubusercontent.com/mateussiqueira/runaway/main/runaway-standalone.sh -o runaway
chmod +x runaway
sudo ./runaway init
```
## De um pendrive USB (para o modo Recovery)
1. Formate um USB/SSD como **FAT32**, **APFS** ou **exFAT**
2. Copie a pasta `unleash` (ou apenas `unleash-standalone.sh`) para o drive
3. Inicialize no Recovery e execute de `/Volumes/SeuDrive/unleash`
2. Copie a pasta `runaway` (ou apenas `runaway-standalone.sh`) para o drive
3. Inicialize no Recovery e execute de `/Volumes/SeuDrive/runaway`
## Via curl no Recovery (precisa de internet)
```bash
curl -L https://raw.githubusercontent.com/mateussiqueira/unleash/main/unleash -o /tmp/unleash
chmod +x /tmp/unleash && /tmp/unleash bypass
curl -L https://raw.githubusercontent.com/mateussiqueira/runaway/main/runaway -o /tmp/runaway
chmod +x /tmp/runaway && /tmp/runaway bypass
```
## Compilando a partir do código-fonte
```bash
git clone https://github.com/mateussiqueira/unleash.git
cd unleash
git clone https://github.com/mateussiqueira/runaway.git
cd runaway
bash examples/build-standalone.sh
# Saída: unleash-standalone.sh (~3200 linhas)
# Saída: runaway-standalone.sh (~3200 linhas)
```
## Verificando a instalação
```bash
./unleash version
# → unleash v2.0.0
./runaway version
# → runaway v2.0.0
./unleash doctor
./runaway doctor
# Executa diagnósticos pré-voo
```
+21 -21
View File
@@ -1,6 +1,6 @@
---
layout: default
title: Cenários — unleash
title: Cenários — runaway
---
# Cenários
@@ -10,8 +10,8 @@ title: Cenários — unleash
Verifique o número serial antes de comprar:
```bash
./unleash predict ABC12345678 # verifica serial contra prefixos conhecidos
./unleash check # este Mac é seguro para limpar?
./runaway predict ABC12345678 # verifica serial contra prefixos conhecidos
./runaway check # este Mac é seguro para limpar?
```
`predict` consulta o serial contra prefixos conhecidos de organizações MDM.
@@ -27,12 +27,12 @@ Se corresponder a JAMF, Mosyle ou outra organização, você sabe o que esperar
**Solução:** Inicialize no Recovery e execute:
```bash
./unleash suppress
./runaway suppress
```
Ou `bypass` se precisar de um novo usuário admin. Remove os marcadores DEP,
artefatos de nível de usuário e preferências MDM que o MA transferiu.
*Este é o caso #1 que a maioria das outras ferramentas não trata — o Unleash lida com ele.*
*Este é o caso #1 que a maioria das outras ferramentas não trata — o Runaway lida com ele.*
---
@@ -43,7 +43,7 @@ artefatos de nível de usuário e preferências MDM que o MA transferiu.
**Solução:**
```bash
sudo ./unleash heal
sudo ./runaway heal
```
Re-desabilita daemons e verifica todas as camadas. Se você executou `persist`
@@ -58,8 +58,8 @@ antes da atualização, isso acontece automaticamente na próxima inicializaçã
**Estratégia:**
1. Inicialize no Recovery **sem conectar ao Wi-Fi**
2. Execute `unleash bypass` antes do dispositivo contatar a Apple
3. Execute `unleash persist` e `unleash whitelist` para mantê-lo limpo
2. Execute `runaway bypass` antes do dispositivo contatar a Apple
3. Execute `runaway persist` e `runaway whitelist` para mantê-lo limpo
4. Só então conecte-se à internet
O serial fica no ABM para sempre — mas enquanto o dispositivo nunca conectar
@@ -70,10 +70,10 @@ com todas as proteções removidas, ele não vai re-registrar.
## Mac usado que já tem um usuário logado
```bash
sudo ./unleash audit # verifica o estado atual
sudo ./unleash harden # mata processos MDM imediatamente
sudo ./unleash whitelist # bloqueia MDM mantendo iCloud
sudo ./unleash persist # sobrevive a atualizações futuras
sudo ./runaway audit # verifica o estado atual
sudo ./runaway harden # mata processos MDM imediatamente
sudo ./runaway whitelist # bloqueia MDM mantendo iCloud
sudo ./runaway persist # sobrevive a atualizações futuras
```
---
@@ -81,7 +81,7 @@ sudo ./unleash persist # sobrevive a atualizações futuras
## Configurando um Mac novo antes do primeiro boot
1. Inicialize no Recovery sem Wi-Fi
2. Execute `unleash init` — assistente interativo
2. Execute `runaway init` — assistente interativo
3. Ele irá: suprimir MDM, instalar persist, instalar whitelist, executar audit
4. Reinicie, configure normalmente, o MDM nunca incomoda
@@ -92,7 +92,7 @@ sudo ./unleash persist # sobrevive a atualizações futuras
Algumas organizações exigem que o Mac registre, mas somente quando conectado à VPN corporativa.
```bash
sudo ./unleash vpn-kill
sudo ./runaway vpn-kill
```
Isso instala um pf kill-switch que bloqueia tráfego MDM quando o dispositivo
@@ -108,8 +108,8 @@ Uma restauração DFU apaga tudo mas não remove a atribuição ABM.
1. Restaure via Apple Configurator 2
2. **Não conecte ao Wi-Fi**
3. Inicialize no Recovery
4. Execute `unleash bypass`
5. Execute `unleash persist && unleash whitelist`
4. Execute `runaway bypass`
5. Execute `runaway persist && runaway whitelist`
6. Reinicie e conecte-se à internet com segurança
---
@@ -120,15 +120,15 @@ Para implantar em múltiplas máquinas:
```bash
# Bypass via script
./unleash suppress --log-file /var/log/unleash-deploy.log
./runaway suppress --log-file /var/log/runaway-deploy.log
# Com persist + monitor
sudo ./unleash persist
sudo ./unleash monitor
sudo ./runaway persist
sudo ./runaway monitor
# Relatório de auditoria em JSON
sudo ./unleash report --json
sudo ./runaway report --json
# Alertas no Discord
sudo ./unleash discord-bot <token> <userId>
sudo ./runaway discord-bot <token> <userId>
```
+3 -3
View File
@@ -1,6 +1,6 @@
---
layout: default
title: Segurança — unleash
title: Segurança — runaway
---
# Segurança & Proteção
@@ -8,7 +8,7 @@ title: Segurança — unleash
## Princípios de Design
### Sem persistência root
O Unleash não instala backdoor, cria usuários ocultos ou modifica o
O Runaway não instala backdoor, cria usuários ocultos ou modifica o
volume do sistema. Todas as alterações miram o **volume de Dados**
apenas e são totalmente reversíveis.
@@ -58,4 +58,4 @@ precisam de acesso à rede.
## Divulgação Responsável
Encontrou um problema de segurança?
Veja a [Política de Segurança](https://github.com/mateussiqueira/unleash/blob/main/SECURITY.md).
Veja a [Política de Segurança](https://github.com/mateussiqueira/runaway/blob/main/SECURITY.md).
+41 -41
View File
@@ -1,6 +1,6 @@
---
layout: default
title: Solução de Problemas — unleash
title: Solução de Problemas — runaway
---
# Solução de Problemas
@@ -16,7 +16,7 @@ A detecção automática de volume falhou.
**Solução:**
1. Execute `diskutil list` para encontrar seu volume de Dados
2. Monte: `diskutil mount /dev/diskXsY`
3. Execute o unleash novamente
3. Execute o runaway novamente
---
@@ -34,11 +34,11 @@ A detecção automática de volume falhou.
Vários comandos precisam de root:
```
[ERR] Firewall needs sudo: sudo ./unleash firewall
[ERR] Heal needs sudo: sudo ./unleash heal
[ERR] Hardening needs sudo: sudo ./unleash harden
[ERR] Audit needs sudo: sudo ./unleash audit
[ERR] Check needs sudo: sudo ./unleash check
[ERR] Firewall needs sudo: sudo ./runaway firewall
[ERR] Heal needs sudo: sudo ./runaway heal
[ERR] Hardening needs sudo: sudo ./runaway harden
[ERR] Audit needs sudo: sudo ./runaway audit
[ERR] Check needs sudo: sudo ./runaway check
```
**Solução:** Anteceda `sudo` ao comando.
@@ -51,18 +51,18 @@ A causa mais comum são **artefatos de nível de usuário** trazidos pelo Migrat
**Solução do Recovery:**
```bash
sudo ./unleash suppress
sudo ./runaway suppress
```
**Solução do sistema já iniciado:**
```bash
sudo ./unleash harden
sudo ./runaway harden
```
Se continuar voltando:
```bash
sudo ./unleash persist # auto-recuperação em cada inicialização
sudo ./unleash monitor # vigia re-registro
sudo ./runaway persist # auto-recuperação em cada inicialização
sudo ./runaway monitor # vigia re-registro
```
---
@@ -73,7 +73,7 @@ Atualizações do sistema restauram os daemons de registro automaticamente.
**Solução:**
```bash
sudo ./unleash heal
sudo ./runaway heal
```
Se você executou `persist` antes da atualização, isso acontece automaticamente na próxima inicialização.
@@ -85,19 +85,19 @@ Se você executou `persist` antes da atualização, isso acontece automaticament
Isso é **cosmético**. O macOS armazena o estado dos perfis no SSV (Volume Selado do Sistema) somente leitura.
**Não confie** em `profiles status -v`.
**Confie** em `unleash status -d`.
**Confie** em `runaway status -d`.
---
### FileVault está ativado
O Unleash detecta FileVault e pede a chave de recuperação ou senha do volume.
O Runaway detecta FileVault e pede a chave de recuperação ou senha do volume.
**Solução:** Se o desbloqueio automático falhar, desbloqueie o volume manualmente no Utilitário de Disco primeiro:
1. Vá para o Utilitário de Disco no Recovery
2. Selecione o volume de Dados
3. Arquivo → Desbloquear → Digite a senha
4. Execute o unleash novamente
4. Execute o runaway novamente
---
@@ -107,7 +107,7 @@ O bloqueio básico de `/etc/hosts` inclui `albert.apple.com` (ativação do iClo
**Solução:** Use `whitelist` em vez do bloqueio básico:
```bash
sudo ./unleash whitelist
sudo ./runaway whitelist
```
Ou remova manualmente estas duas linhas de `/etc/hosts`:
@@ -133,14 +133,14 @@ Ou remova manualmente estas duas linhas de `/etc/hosts`:
### Monitor não inicia
**Verifique:**
1. Já está rodando? `sudo ./unleash monitor-status`
1. Já está rodando? `sudo ./runaway monitor-status`
2. Permissões: precisa de root
3. Logs: `/var/log/unleash-monitor.log`
3. Logs: `/var/log/runaway-monitor.log`
**Solução:**
```bash
sudo ./unleash monitor-stop
sudo ./unleash monitor
sudo ./runaway monitor-stop
sudo ./runaway monitor
```
---
@@ -150,7 +150,7 @@ sudo ./unleash monitor
O modo Recovery não tem internet por padrão.
**Solução:**
1. Use um pendrive USB com o unleash copiado
1. Use um pendrive USB com o runaway copiado
2. Ou conecte-se ao Wi-Fi no Recovery (menu superior direito → ícone Wi-Fi)
---
@@ -161,10 +161,10 @@ O modo Recovery não tem internet por padrão.
ERROR: Library not found: /path/to/lib/colors.sh
```
**Causa:** Executando o script `unleash` fonte de fora do diretório do repositório.
**Causa:** Executando o script `runaway` fonte de fora do diretório do repositório.
**Solução:**
- Use a versão standalone (`unleash-standalone.sh`)
- Use a versão standalone (`runaway-standalone.sh`)
- Ou execute da raiz do repositório onde o diretório `lib/` existe
- Ou instale via Homebrew
@@ -176,8 +176,8 @@ pf pode ter regras existentes que conflitam.
**Solução:**
```bash
sudo ./unleash firewall-off # limpa regras existentes
sudo ./unleash firewall # reaplica
sudo ./runaway firewall-off # limpa regras existentes
sudo ./runaway firewall # reaplica
```
---
@@ -189,8 +189,8 @@ Uma restauração DFU/IPSW completa não remove a atribuição ABM — o serial
**Estratégia:**
1. Após restaurar, **não conecte ao Wi-Fi**
2. Inicialize no Recovery
3. Execute `unleash bypass` antes do dispositivo contatar a Apple
4. Execute `unleash persist` e `unleash whitelist`
3. Execute `runaway bypass` antes do dispositivo contatar a Apple
4. Execute `runaway persist` e `runaway whitelist`
5. Só então conecte-se à internet
O serial fica no ABM para sempre — mas se o dispositivo nunca conectar sem proteções, ele não vai re-registrar.
@@ -206,8 +206,8 @@ O serial fica no ABM para sempre — mas se o dispositivo nunca conectar sem pro
**Solução:**
1. Certifique-se de ter `gpg` instalado
2. Importe a chave de assinatura: `gpg --keyserver keys.openpgp.org --recv-key <KEY_ID>`
3. Tente `sudo ./unleash update` novamente
4. Ou baixe manualmente de [GitHub Releases](https://github.com/mateussiqueira/unleash/releases)
3. Tente `sudo ./runaway update` novamente
4. Ou baixe manualmente de [GitHub Releases](https://github.com/mateussiqueira/runaway/releases)
---
@@ -219,9 +219,9 @@ Error: ... homebrew-core ...
**Solução:** Certifique-se de que o tap está atualizado:
```bash
brew untap mateussiqueira/unleash
brew tap mateussiqueira/unleash
brew install unleash
brew untap mateussiqueira/runaway
brew tap mateussiqueira/runaway
brew install runaway
```
---
@@ -234,7 +234,7 @@ Todos os comandos produzem logs estruturados:
[INF] Data volume: /Volumes/Macintosh HD - Data
[ OK] Admin 'apple' created (UID 501)
[WRN] DEP activation record present
[ERR] Firewall needs sudo: sudo ./unleash firewall
[ERR] Firewall needs sudo: sudo ./runaway firewall
[STP] Locating Data volume by APFS role...
[DBG] Checking pfctl availability
```
@@ -252,7 +252,7 @@ Todos os comandos produzem logs estruturados:
Use `--verbose` para mensagens de debug e `--log-file <caminho>` para salvar em um arquivo:
```bash
sudo ./unleash heal --verbose --log-file /tmp/unleash.log
sudo ./runaway heal --verbose --log-file /tmp/runaway.log
```
---
@@ -263,22 +263,22 @@ Execute estes para coletar informações antes de buscar ajuda:
```bash
# Verificação rápida de saúde
sudo ./unleash doctor
sudo ./runaway doctor
# Auditoria completa do sistema
sudo ./unleash audit
sudo ./runaway audit
# Gerar relatório
sudo ./unleash report
sudo ./runaway report
# Simular um bypass
sudo ./unleash demo
sudo ./runaway demo
```
---
## Obtendo Ajuda
- [GitHub Issues](https://github.com/mateussiqueira/unleash/issues)
- [Discussões](https://github.com/mateussiqueira/unleash/discussions)
- [Política de Segurança](https://github.com/mateussiqueira/unleash/blob/main/SECURITY.md)
- [GitHub Issues](https://github.com/mateussiqueira/runaway/issues)
- [Discussões](https://github.com/mateussiqueira/runaway/discussions)
- [Política de Segurança](https://github.com/mateussiqueira/runaway/blob/main/SECURITY.md)
+21 -21
View File
@@ -1,6 +1,6 @@
---
layout: default
title: Scenarios — unleash
title: Scenarios — runaway
---
# Scenarios
@@ -10,8 +10,8 @@ title: Scenarios — unleash
Check the serial number before you buy:
```bash
./unleash predict ABC12345678 # check serial against known org prefixes
./unleash check # is this Mac safe to wipe?
./runaway predict ABC12345678 # check serial against known org prefixes
./runaway check # is this Mac safe to wipe?
```
`predict` looks up the device serial against known MDM org prefixes.
@@ -27,12 +27,12 @@ If it matches JAMF, Mosyle, or another org, you know what you're dealing with be
**Fix:** Boot to Recovery and run:
```bash
./unleash suppress
./runaway suppress
```
Or `bypass` if you need a new admin user. This removes the DEP markers,
user-level artifacts, and MDM preferences that MA transferred over.
*This is the #1 case most other tools miss — Unleash handles it.*
*This is the #1 case most other tools miss — Runaway handles it.*
---
@@ -43,7 +43,7 @@ user-level artifacts, and MDM preferences that MA transferred over.
**Fix:**
```bash
sudo ./unleash heal
sudo ./runaway heal
```
Re-disables daemons and re-checks all layers. If you ran `persist`
@@ -58,8 +58,8 @@ before the update, this happens automatically on the next boot.
**Strategy:**
1. Boot to Recovery **without connecting to Wi-Fi**
2. Run `unleash bypass` before the device ever phones home
3. Run `unleash persist` and `unleash whitelist` so it stays clean
2. Run `runaway bypass` before the device ever phones home
3. Run `runaway persist` and `runaway whitelist` so it stays clean
4. Only then connect to the internet
The serial stays in ABM forever — but as long as the device never
@@ -70,10 +70,10 @@ connects with full protections removed, it will not re-enroll.
## Used Mac that already has a user logged in
```bash
sudo ./unleash audit # check current state
sudo ./unleash harden # kill MDM processes immediately
sudo ./unleash whitelist # block MDM while keeping iCloud
sudo ./unleash persist # survive future updates
sudo ./runaway audit # check current state
sudo ./runaway harden # kill MDM processes immediately
sudo ./runaway whitelist # block MDM while keeping iCloud
sudo ./runaway persist # survive future updates
```
---
@@ -81,7 +81,7 @@ sudo ./unleash persist # survive future updates
## Setting up a new Mac before first boot
1. Boot to Recovery without Wi-Fi
2. Run `unleash init` — interactive wizard
2. Run `runaway init` — interactive wizard
3. It will: suppress MDM, install persist, install whitelist, run audit
4. Reboot, set up normally, MDM never bothers you
@@ -92,7 +92,7 @@ sudo ./unleash persist # survive future updates
Some organizations require the Mac to enroll but only when connected to the corporate VPN.
```bash
sudo ./unleash vpn-kill
sudo ./runaway vpn-kill
```
This installs a pf kill-switch that blocks MDM traffic when the device
@@ -108,8 +108,8 @@ A DFU restore erases everything but doesn't remove ABM assignment.
1. Restore via Apple Configurator 2
2. **Do not connect to Wi-Fi**
3. Boot to Recovery
4. Run `unleash bypass`
5. Run `unleash persist && unleash whitelist`
4. Run `runaway bypass`
5. Run `runaway persist && runaway whitelist`
6. Reboot and connect to the internet safely
---
@@ -120,15 +120,15 @@ For deploying across multiple machines:
```bash
# Scripted bypass
./unleash suppress --log-file /var/log/unleash-deploy.log
./runaway suppress --log-file /var/log/runaway-deploy.log
# With persist + monitor
sudo ./unleash persist
sudo ./unleash monitor
sudo ./runaway persist
sudo ./runaway monitor
# Audit report in JSON
sudo ./unleash report --json
sudo ./runaway report --json
# Discord alerts
sudo ./unleash discord-bot <token> <userId>
sudo ./runaway discord-bot <token> <userId>
```
+3 -3
View File
@@ -1,6 +1,6 @@
---
layout: default
title: Security — unleash
title: Security — runaway
---
# Security & Safety
@@ -8,7 +8,7 @@ title: Security — unleash
## Design Principles
### No root persistence
Unleash does not install backdoors, create hidden users, or modify the
Runaway does not install backdoors, create hidden users, or modify the
system volume. All changes target the **Data volume** only and are
fully reversible.
@@ -58,4 +58,4 @@ network access.
## Responsible Disclosure
Found a security issue?
See the [Security Policy](https://github.com/mateussiqueira/unleash/blob/main/SECURITY.md).
See the [Security Policy](https://github.com/mateussiqueira/runaway/blob/main/SECURITY.md).
+3 -3
View File
@@ -19,10 +19,10 @@
<circle cx="128" cy="164" r="8" fill="#f38ba8"/>
<circle cx="152" cy="164" r="8" fill="#fab387"/>
<circle cx="176" cy="164" r="8" fill="#a6e3a1"/>
<text x="600" y="170" fill="#6c7086" text-anchor="middle" font-family="SFMono-Regular,Consolas,monospace" font-size="20">unleash — terminal</text>
<text x="600" y="170" fill="#6c7086" text-anchor="middle" font-family="SFMono-Regular,Consolas,monospace" font-size="20">runaway — terminal</text>
<!-- Code lines -->
<text x="140" y="240" fill="#89b4fa" font-family="SFMono-Regular,Consolas,monospace" font-size="22">$ sudo ./unleash bypass</text>
<text x="140" y="240" fill="#89b4fa" font-family="SFMono-Regular,Consolas,monospace" font-size="22">$ sudo ./runaway bypass</text>
<text x="140" y="290" fill="#a6e3a1" font-family="SFMono-Regular,Consolas,monospace" font-size="20">✓ MDM domains blocked (13/13)</text>
<text x="140" y="330" fill="#a6e3a1" font-family="SFMono-Regular,Consolas,monospace" font-size="20">✓ DEP enrollment markers removed</text>
@@ -34,7 +34,7 @@
<text x="600" y="470" fill="#a6e3a1" text-anchor="middle" font-family="SFMono-Regular,Consolas,monospace" font-size="24" font-weight="bold">MDM BYPASSED — reboot and enjoy</text>
<!-- Footer -->
<text x="600" y="560" fill="#6c7086" text-anchor="middle" font-family="SFMono-Regular,Consolas,monospace" font-size="18">github.com/mateussiqueira/unleash</text>
<text x="600" y="560" fill="#6c7086" text-anchor="middle" font-family="SFMono-Regular,Consolas,monospace" font-size="18">github.com/mateussiqueira/runaway</text>
<!-- Cursor blink -->
<rect x="380" y="226" width="14" height="26" fill="#cdd6f4" rx="3">

Before

Width:  |  Height:  |  Size: 2.4 KiB

After

Width:  |  Height:  |  Size: 2.4 KiB

+41 -41
View File
@@ -1,6 +1,6 @@
---
layout: default
title: Troubleshooting — unleash
title: Troubleshooting — runaway
---
# Troubleshooting
@@ -16,7 +16,7 @@ Volume auto-detection failed.
**Fix:**
1. Run `diskutil list` to find your Data volume
2. Mount it: `diskutil mount /dev/diskXsY`
3. Re-run unleash
3. Re-run runaway
---
@@ -34,11 +34,11 @@ Volume auto-detection failed.
Various commands require root:
```
[ERR] Firewall needs sudo: sudo ./unleash firewall
[ERR] Heal needs sudo: sudo ./unleash heal
[ERR] Hardening needs sudo: sudo ./unleash harden
[ERR] Audit needs sudo: sudo ./unleash audit
[ERR] Check needs sudo: sudo ./unleash check
[ERR] Firewall needs sudo: sudo ./runaway firewall
[ERR] Heal needs sudo: sudo ./runaway heal
[ERR] Hardening needs sudo: sudo ./runaway harden
[ERR] Audit needs sudo: sudo ./runaway audit
[ERR] Check needs sudo: sudo ./runaway check
```
**Fix:** Prepend `sudo` to the command.
@@ -51,18 +51,18 @@ The most common cause is **user-level artifacts** carried over by Migration Assi
**Fix from Recovery:**
```bash
sudo ./unleash suppress
sudo ./runaway suppress
```
**Fix from booted system:**
```bash
sudo ./unleash harden
sudo ./runaway harden
```
If it keeps returning:
```bash
sudo ./unleash persist # auto-heal on every boot
sudo ./unleash monitor # watch for re-enrollment
sudo ./runaway persist # auto-heal on every boot
sudo ./runaway monitor # watch for re-enrollment
```
---
@@ -73,7 +73,7 @@ System updates restore enrollment daemons automatically.
**Fix:**
```bash
sudo ./unleash heal
sudo ./runaway heal
```
If you ran `persist` before the update, this runs automatically on next boot.
@@ -85,19 +85,19 @@ If you ran `persist` before the update, this runs automatically on next boot.
This is **cosmetic**. macOS stores profile state on the read-only SSV (System Sealed Volume).
**Don't trust** `profiles status -v`.
**Trust** `unleash status -d` instead.
**Trust** `runaway status -d` instead.
---
### FileVault is enabled
Unleash detects FileVault and prompts for the recovery key or volume password.
Runaway detects FileVault and prompts for the recovery key or volume password.
**Fix:** If automatic unlock fails, unlock the volume manually in Disk Utility first:
1. Go to Disk Utility in Recovery
2. Select the Data volume
3. File → Unlock → Enter password
4. Re-run unleash
4. Re-run runaway
---
@@ -107,7 +107,7 @@ The basic `/etc/hosts` block includes `albert.apple.com` (iCloud activation) and
**Fix:** Use `whitelist` instead of the basic block:
```bash
sudo ./unleash whitelist
sudo ./runaway whitelist
```
Or manually remove these two lines from `/etc/hosts`:
@@ -133,14 +133,14 @@ Or manually remove these two lines from `/etc/hosts`:
### Monitor won't start
**Check:**
1. Is it already running? `sudo ./unleash monitor-status`
1. Is it already running? `sudo ./runaway monitor-status`
2. Permissions: needs root
3. Check logs: `/var/log/unleash-monitor.log`
3. Check logs: `/var/log/runaway-monitor.log`
**Fix:**
```bash
sudo ./unleash monitor-stop
sudo ./unleash monitor
sudo ./runaway monitor-stop
sudo ./runaway monitor
```
---
@@ -150,7 +150,7 @@ sudo ./unleash monitor
Recovery mode has no internet by default.
**Fix:**
1. Use a USB drive with unleash copied to it
1. Use a USB drive with runaway copied to it
2. Or connect to Wi-Fi in Recovery (top-right menu → Wi-Fi icon)
---
@@ -161,10 +161,10 @@ Recovery mode has no internet by default.
ERROR: Library not found: /path/to/lib/colors.sh
```
**Cause:** Running the source `unleash` script from outside the repo directory.
**Cause:** Running the source `runaway` script from outside the repo directory.
**Fix:**
- Use the standalone version (`unleash-standalone.sh`) instead
- Use the standalone version (`runaway-standalone.sh`) instead
- Or run from the repo root where the `lib/` directory exists
- Or install via Homebrew
@@ -176,8 +176,8 @@ pf might have existing rules that conflict.
**Fix:**
```bash
sudo ./unleash firewall-off # clear existing rules
sudo ./unleash firewall # re-apply
sudo ./runaway firewall-off # clear existing rules
sudo ./runaway firewall # re-apply
```
---
@@ -189,8 +189,8 @@ A full DFU/IPSW restore doesn't remove ABM assignment — the serial stays in Ap
**Strategy:**
1. After restore, **do not connect to Wi-Fi**
2. Boot to Recovery
3. Run `unleash bypass` before the device ever phones home
4. Run `unleash persist` and `unleash whitelist`
3. Run `runaway bypass` before the device ever phones home
4. Run `runaway persist` and `runaway whitelist`
5. Only then connect to the internet
The serial stays in ABM forever — but if the device never connects without protections, it won't re-enroll.
@@ -206,8 +206,8 @@ The serial stays in ABM forever — but if the device never connects without pro
**Fix:**
1. Make sure you have `gpg` installed
2. Import the signing key: `gpg --keyserver keys.openpgp.org --recv-key <KEY_ID>`
3. Try `sudo ./unleash update` again
4. Or download manually from [GitHub Releases](https://github.com/mateussiqueira/unleash/releases)
3. Try `sudo ./runaway update` again
4. Or download manually from [GitHub Releases](https://github.com/mateussiqueira/runaway/releases)
---
@@ -219,9 +219,9 @@ Error: ... homebrew-core ...
**Fix:** Make sure the tap is up to date:
```bash
brew untap mateussiqueira/unleash
brew tap mateussiqueira/unleash
brew install unleash
brew untap mateussiqueira/runaway
brew tap mateussiqueira/runaway
brew install runaway
```
---
@@ -234,7 +234,7 @@ All commands produce structured logs:
[INF] Data volume: /Volumes/Macintosh HD - Data
[ OK] Admin 'apple' created (UID 501)
[WRN] DEP activation record present
[ERR] Firewall needs sudo: sudo ./unleash firewall
[ERR] Firewall needs sudo: sudo ./runaway firewall
[STP] Locating Data volume by APFS role...
[DBG] Checking pfctl availability
```
@@ -252,7 +252,7 @@ All commands produce structured logs:
Use `--verbose` for debug messages and `--log-file <path>` to save to a file:
```bash
sudo ./unleash heal --verbose --log-file /tmp/unleash.log
sudo ./runaway heal --verbose --log-file /tmp/runaway.log
```
---
@@ -263,22 +263,22 @@ Run these to gather information before seeking help:
```bash
# Quick health check
sudo ./unleash doctor
sudo ./runaway doctor
# Full system audit
sudo ./unleash audit
sudo ./runaway audit
# Generate report
sudo ./unleash report
sudo ./runaway report
# Dry-run a bypass
sudo ./unleash demo
sudo ./runaway demo
```
---
## Getting Help
- [GitHub Issues](https://github.com/mateussiqueira/unleash/issues)
- [Discussions](https://github.com/mateussiqueira/unleash/discussions)
- [Security Policy](https://github.com/mateussiqueira/unleash/blob/main/SECURITY.md)
- [GitHub Issues](https://github.com/mateussiqueira/runaway/issues)
- [Discussions](https://github.com/mateussiqueira/runaway/discussions)
- [Security Policy](https://github.com/mateussiqueira/runaway/blob/main/SECURITY.md)