rename project to runaway
This commit is contained in:
+49
-49
@@ -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)
|
||||
|
||||
Reference in New Issue
Block a user