rename project to runaway

This commit is contained in:
2026-11-09 10:13:51 +08:00
parent 20946dd445
commit 205f2faf02
95 changed files with 1034 additions and 1034 deletions
+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>
```