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