Skip to content

Run a virtual iPhone on an Apple Silicon Mac.

Swift

build: wire vphone-amfi-allow and vphone-ask-for-permission in

Lakr236ea3376e55
diff --git a/Makefile b/Makefile
index 917a523c..408186a1 100644
--- a/Makefile
+++ b/Makefile
@@ -39,16 +39,24 @@ SCRIPTS := scripts
# holds the private virtualization keys and is what amfid can refuse;
# vphone-archive unpacks and packs. See sources/vphone.entitlements.
#
-# Opening an AMFI window for vphone-vm is the USER's job — this project no
-# longer ships a tool for it. `make amfi_command` prints the command line.
+# Getting vphone-vm past amfid is `make amfi_allow`, which runs
+# vphone-amfi-allow for this build's cdhashes. It asks for root and it is a
+# per-build step. `make amfi_off` puts the machine back.
BINARY := .build/release/vphone-cli
VM_BINARY := .build/release/vphone-vm
ARCHIVE_BINARY := .build/release/vphone-archive
+ASKPASS_BINARY := .build/release/vphone-ask-for-permission
+# Not a SwiftPM product: SwiftPM emits arm64 and this one must be arm64e to
+# read amfid's ObjC runtime. Built by clang, below and in scripts/build.sh.
+AMFI_BINARY := .build/release/vphone-amfi-allow
+AMFI_SOURCE := sources/vphone-amfi-allow/vphone-amfi-allow.c
PATCHER_BINARY := .build/debug/vphone-cli
BUNDLE := .build/vphone-cli.app
BUNDLE_BIN := $(BUNDLE)/Contents/MacOS/vphone-cli
BUNDLE_VM := $(BUNDLE)/Contents/MacOS/vphone-vm
BUNDLE_ARCHIVE := $(BUNDLE)/Contents/MacOS/vphone-archive
+BUNDLE_ASKPASS := $(BUNDLE)/Contents/MacOS/vphone-ask-for-permission
+BUNDLE_AMFI := $(BUNDLE)/Contents/MacOS/vphone-amfi-allow
INFO_PLIST := sources/Info.plist
ENTITLEMENTS := sources/vphone.entitlements
# There is no interpreter here any more, and no variable naming one. The
@@ -109,8 +117,10 @@ help:
@echo " Options: BACKUP_INCLUDE_IPSW=1 Include *_Restore* IPSW directories in the backup"
@echo " FORCE=1 Skip overwrite prompt on restore"
@echo " make check-aux Run the self-containment admission gates"
- @echo " make amfi_command Print the 'sudo amfidont daemon …' line for this build"
- @echo " (prints only — installs nothing, runs nothing, needs no sudo)"
+ @echo " make amfi_allow Allow THIS build's vphone-vm past amfid (asks for root)"
+ @echo " Re-run after every build — it allowlists cdhashes"
+ @echo " make amfi_status Show the allowlist and whether this host can carry one"
+ @echo " make amfi_off Remove the allowlist and restart amfid clean"
@echo " make boot_host_preflight Diagnose whether host can launch signed PV=3 binary"
@echo " make boot Boot VM (reads from config.plist)"
@echo " make boot_less Boot VM in vphoned patchless compatibility mode"
@@ -262,7 +272,8 @@ $(BINARY): $(SWIFT_SOURCES) Package.swift $(ENTITLEMENTS)
@codesign --force --sign - --entitlements $(ENTITLEMENTS) $(VM_BINARY)
@codesign --force --sign - $(BINARY)
@codesign --force --sign - $(ARCHIVE_BINARY)
- @echo " signed: vphone-vm (entitled), vphone-cli, vphone-archive"
+ @codesign --force --sign - $(ASKPASS_BINARY)
+ @echo " signed: vphone-vm (entitled), vphone-cli, vphone-archive, vphone-ask-for-permission"
@# An unentitled vphone-vm is worse than a broken one: it launches
@# perfectly, which convinces vphone-cli's AMFI probe that nothing is
@# wrong, and only fails later trying to create a PV=3 machine. A bare
@@ -271,13 +282,28 @@ $(BINARY): $(SWIFT_SOURCES) Package.swift $(ENTITLEMENTS)
| grep -q 'com.apple.private.virtualization' \
|| (echo "Error: $(VM_BINARY) is not entitled after signing." >&2; exit 1)
-$(VM_BINARY) $(ARCHIVE_BINARY): $(BINARY)
-
-bundle: build $(INFO_PLIST)
+$(VM_BINARY) $(ARCHIVE_BINARY) $(ASKPASS_BINARY): $(BINARY)
+
+# arm64e, because it reads amfid's ObjC runtime and has to match amfid's slice.
+# An arm64 build links and then fails at run time with nothing to say, so the
+# slice is asserted rather than assumed.
+$(AMFI_BINARY): $(AMFI_SOURCE)
+ @echo "=== Building vphone-amfi-allow (arm64e) ==="
+ @mkdir -p $(dir $(AMFI_BINARY))
+ @clang -arch arm64e -O2 -framework CoreFoundation -framework Security \
+ -o $(AMFI_BINARY) $(AMFI_SOURCE)
+ @file $(AMFI_BINARY) | grep -q arm64e \
+ || (echo "Error: $(AMFI_BINARY) is not arm64e." >&2; exit 1)
+ @codesign --force --sign - $(AMFI_BINARY)
+ @echo " signed: vphone-amfi-allow"
+
+bundle: build $(AMFI_BINARY) $(INFO_PLIST)
@mkdir -p $(BUNDLE)/Contents/MacOS $(BUNDLE)/Contents/Resources
@cp -f $(BINARY) $(BUNDLE_BIN)
@cp -f $(VM_BINARY) $(BUNDLE_VM)
@cp -f $(ARCHIVE_BINARY) $(BUNDLE_ARCHIVE)
+ @cp -f $(ASKPASS_BINARY) $(BUNDLE_ASKPASS)
+ @cp -f $(AMFI_BINARY) $(BUNDLE_AMFI)
@cp -f $(INFO_PLIST) $(BUNDLE)/Contents/Info.plist
@cp -f sources/AppIcon.icns $(BUNDLE)/Contents/Resources/AppIcon.icns
@cp -f $(SCRIPTS)/vphoned/signcert.p12 $(BUNDLE)/Contents/Resources/signcert.p12
@@ -296,6 +322,8 @@ bundle: build $(INFO_PLIST)
@# nested binaries FIRST, or `codesign -v` reports "nested code is modified".
@codesign --force --sign - $(BUNDLE_BIN)
@codesign --force --sign - $(BUNDLE_ARCHIVE)
+ @codesign --force --sign - $(BUNDLE_ASKPASS)
+ @codesign --force --sign - $(BUNDLE_AMFI)
@codesign --force --sign - --entitlements $(ENTITLEMENTS) $(BUNDLE_VM)
@codesign -v $(BUNDLE_VM) \
|| (echo "Error: the bundle seal did not verify after signing." >&2; exit 1)
@@ -319,7 +347,7 @@ vphoned:
# VM management
# ═══════════════════════════════════════════════════════════════════
-.PHONY: vm_new vm_backup vm_restore vm_switch vm_list amfi_command boot_host_preflight boot boot_less boot_dfu boot_binary_check boot_binary_check_less
+.PHONY: vm_new vm_backup vm_restore vm_switch vm_list amfi_allow amfi_status amfi_off boot_host_preflight boot boot_less boot_dfu boot_binary_check boot_binary_check_less
vm_new:
CPU="$(CPU)" MEMORY="$(MEMORY)" \
@@ -364,56 +392,49 @@ check-aux: bundle
@zsh $(SCRIPTS)/check_aux.sh
# vphone-vm carries the private virtualization entitlements, so amfid is the one
-# thing that can refuse it. Opening a window for it is the user's own business:
-# this project ships no bypass and depends on none. What it can do is save the
-# cdhash from being copied out of `codesign -dv` by hand, so this target prints
-# the exact command line for the binaries THIS build produced — and prints only.
-# It installs nothing, runs nothing, needs no sudo, and does not care whether
-# amfidont is on the machine at all.
+# thing that can refuse it. `vphone-amfi-allow` is how this project gets past
+# that, and this target runs it for the binaries THIS build produced.
+#
+# It needs root, and it asks — it does not assume a passwordless sudo and it
+# does not hold a password. It needs `Debugging Restrictions: disabled` in
+# `csrutil status` as well, for task_for_pid; without it the tool says so and
+# changes nothing.
#
# It depends on `bundle` because `make boot` needs BOTH copies of vphone-vm let
# through: boot_binary_check runs .build/release/vphone-vm, and the boot itself
# runs the one inside the .app. Their cdhashes differ — different signing
# identifier (`vphone-vm-<hash>` vs `com.vphone.cli`), sealed bundle resources
# on one and none on the other, and they are not even the same length — so an
-# allowlist given one cdhash covers exactly half the flow.
+# allowlist given one cdhash covers exactly half the flow. Both are passed.
#
-# The paths are printed resolved (`pwd -P`). .build/release is a symlink to
-# .build/out/Products/Release, and amfid judges the vnode path it is handed,
-# not the symlink the user typed — a `--path` entry naming the symlink matches
-# nothing, silently.
-amfi_command: bundle
+# The paths are resolved (`pwd -P`). .build/release is a symlink to
+# .build/out/Products/Release, and the requirement is evaluated against the
+# vnode path, not the symlink that was typed.
+amfi_allow: bundle
@set -e; \
- paths=""; hashes=""; \
+ binaries=""; \
for b in "$(CURDIR)/$(VM_BINARY)" "$(CURDIR)/$(BUNDLE_VM)"; do \
[ -f "$$b" ] || continue; \
- h="$$(codesign -dv --verbose=4 "$$b" 2>&1 | sed -n 's/^CDHash=//p' | head -1)"; \
- [ -n "$$h" ] || continue; \
d="$$(cd "$$(dirname "$$b")" && pwd -P)"; \
- case " $$paths " in *" $$d "*) ;; *) paths="$$paths $$d";; esac; \
- case " $$hashes " in *" $$h "*) ;; *) hashes="$$hashes $$h";; esac; \
+ binaries="$$binaries $$d/$$(basename "$$b")"; \
done; \
- if [ -z "$$hashes" ]; then \
- echo "Error: no CDHash on $(VM_BINARY) — run 'make build' first." >&2; \
+ if [ -z "$$binaries" ]; then \
+ echo "Error: $(VM_BINARY) not built — run 'make build' first." >&2; \
exit 1; \
fi; \
- echo "vphone-vm is the only entitled binary, so it is the only one amfid can"; \
- echo "refuse. Allow it with an AMFI bypass of your choosing — the project does"; \
- echo "not install, start or require one. With amfidont, for this build:"; \
- echo ""; \
- printf ' sudo amfidont daemon'; \
- for d in $$paths; do printf " \\\\\n --path '%s'" "$$d"; done; \
- for h in $$hashes; do printf " \\\\\n --cdhash %s" "$$h"; done; \
- printf " \\\\\n --spoof-apple --verbose\n"; \
+ echo "Allowing this build past amfid (needs root):"; \
+ for b in $$binaries; do echo " $$b"; done; \
echo ""; \
- echo "It is an allowlist: only the paths and cdhashes above are let through."; \
- echo "Re-run this target after every build — the cdhash changes with the binary."; \
- echo "Leave the daemon running in its own terminal, then 'make boot' in another."; \
- echo ""; \
- echo "amfidont is not part of this project and is not built here."; \
- echo "It installs with the SYSTEM python (Homebrew's refuses, PEP 668):"; \
- echo " xcrun python3 -m pip install --user amfidont # needs Xcode"; \
- echo " ~/Library/Python/3.9/bin/amfidont"
+ sudo "$(CURDIR)/$(AMFI_BINARY)" allow $$binaries
+
+# What the allowlist looks like right now, and whether the host can carry one.
+# Reads only; no root.
+amfi_status: $(AMFI_BINARY)
+ @"$(CURDIR)/$(AMFI_BINARY)" status
+
+# Put the machine back: drops the preference and restarts amfid clean.
+amfi_off:
+ @sudo "$(CURDIR)/$(AMFI_BINARY)" off
boot_host_preflight: build
zsh $(SCRIPTS)/boot_host_preflight.sh
@@ -431,9 +452,9 @@ define BOOT_BINARY_CHECK
if [ $$rc -ne 0 ]; then \
echo "Error: signed vphone-vm failed to launch (exit $$rc)." >&2; \
echo "Check private virtualization entitlement support and ensure SIP/AMFI are disabled on the host." >&2; \
- echo "If it was SIGKILLed, amfid refused the entitlements and an AMFI bypass has to allow" >&2; \
- echo "vphone-vm first. That is yours to run; for the command line, with this build's cdhash:" >&2; \
- echo " make amfi_command" >&2; \
+ echo "If it was SIGKILLed, amfid refused the entitlements and this build has to be" >&2; \
+ echo "allowed past it first. That step needs root, so it is not run for you:" >&2; \
+ echo " make amfi_allow" >&2; \
if [ -s "$$tmp_log" ]; then \
echo "--- vphone-cli preflight log ---" >&2; \
tail -n 40 "$$tmp_log" >&2; \
diff --git a/Package.swift b/Package.swift
index 18d00b5e..e9e2e4db 100644
--- a/Package.swift
+++ b/Package.swift
@@ -262,12 +262,25 @@ let package = Package(
],
path: "sources/vphone-archive"
),
- // A `vphone-letmein` target stood here: a C program that wrote amfid's
- // __TEXT to open a short window for vphone-vm. It cannot work on a host
- // where `vm.cs_system_enforcement` is 1 — the dirtied page is exactly
- // what gets amfid SIGKILLed — and opening an AMFI window is the user's
- // decision to make, not this project's. See "SIP/AMFI Relaxation" in
- // README.md for the two routes that do work.
+ // The SUDO_ASKPASS program, and the probe behind `VPhoneSudo.route()`.
+ // No ArgumentParser and no VPhoneCore: it is two verbs, it runs while
+ // sudo waits on its stdout, and `VPhoneSudo` in VPhoneCore shells out
+ // to it rather than linking it — a dependency the other way round would
+ // put AppKit under vphone-cli.
+ .executableTarget(
+ name: "vphone-ask-for-permission",
+ path: "sources/vphone-ask-for-permission"
+ ),
+ // `vphone-amfi-allow` is NOT here, and cannot be: SwiftPM emits arm64
+ // and it has to be arm64e to read amfid's ObjC runtime. `scripts/build.sh`
+ // compiles it with clang; see the header of its one C file.
+ //
+ // A `vphone-letmein` target stood here too: a C program that wrote
+ // amfid's __TEXT to open a short window for vphone-vm. It cannot work on
+ // a host where `vm.cs_system_enforcement` is 1 — the dirtied page is
+ // exactly what gets amfid SIGKILLed. `vphone-amfi-allow` replaces it by
+ // writing one byte of amfid's *heap* instead, which that sysctl does not
+ // police. See "SIP/AMFI Relaxation" in README.md.
.testTarget(
name: "FirmwarePatcherTests",
dependencies: ["FirmwarePatcher"],
diff --git a/scripts/boot_host_preflight.sh b/scripts/boot_host_preflight.sh
index bef52006..d34eebb6 100755
--- a/scripts/boot_host_preflight.sh
+++ b/scripts/boot_host_preflight.sh
@@ -182,11 +182,10 @@ echo "If unsigned debug runs but either signed binary exits 137 / signal 9,"
echo "the host is not currently permitting the required private virtualization entitlements."
echo "If the signed release binary exits 0 but the signed debug control still exits 137,"
echo "something is permitting this particular binary and not others — and with an"
-echo "allowlist-style AMFI bypass, such as amfidont, that is the EXPECTED result, not"
-echo "a contradiction: it allows only the paths and CDHashes it was given, and the"
-echo "debug control above is a fresh copy in a temp directory with its own CDHash."
-echo "This project ships no bypass and starts none; running one is yours to do."
-echo "'make amfi_command' prints the command line, with this build's CDHash filled in."
+echo "allowlist, which is what 'make amfi_allow' installs, that is the EXPECTED result,"
+echo "not a contradiction: it allows only the binaries it was given, and the debug"
+echo "control above is a fresh copy in a temp directory with its own CDHash."
+echo "'make amfi_allow' covers this build; it needs root and is not run for you."
echo "Typical requirements for this project are:"
echo " 1. macOS 15+ with PV=3 support"
echo " 2. Host hardware must expose Virtualization.framework VM support (not a nested VM without virtualization availability)"
diff --git a/scripts/build.sh b/scripts/build.sh
index 945dcd7e..dce8938a 100755
--- a/scripts/build.sh
+++ b/scripts/build.sh
@@ -16,21 +16,30 @@ SCRIPT_DIR="${0:A:h}"
PROJECT_ROOT="${SCRIPT_DIR:h}"
cd "$PROJECT_ROOT"
-# Three host binaries, and only ONE of them is entitled. vphone-cli is the
+# Five host binaries, and only ONE of them is entitled. vphone-cli is the
# user-facing entry point and carries nothing, so it always launches; vphone-vm
# holds the private virtualization keys and is what amfid can refuse;
-# vphone-archive unpacks and packs without gtar, bsdtar, unzip or zstd.
+# vphone-archive unpacks and packs without gtar, bsdtar, unzip or zstd;
+# vphone-ask-for-permission is the SUDO_ASKPASS helper; vphone-amfi-allow is
+# what gets vphone-vm past amfid.
#
-# Nothing here opens an AMFI window. Allowing vphone-vm past amfid is the user's
-# own step, with a bypass this project neither ships nor depends on; `make
-# amfi_command` prints the command line for the binaries built below.
+# `make amfi_allow` runs that last one for the binaries built below. It is a
+# per-build step, not a once-per-machine one, because it allowlists cdhashes and
+# those change every time anything is signed.
BINARY=".build/release/vphone-cli"
VM_BINARY=".build/release/vphone-vm"
ARCHIVE_BINARY=".build/release/vphone-archive"
+ASKPASS_BINARY=".build/release/vphone-ask-for-permission"
+# Not built by `swift build`: SwiftPM emits arm64 and this one has to be arm64e
+# to walk amfid's ObjC runtime. See the header of its C file.
+AMFI_BINARY=".build/release/vphone-amfi-allow"
+AMFI_SOURCE="sources/vphone-amfi-allow/vphone-amfi-allow.c"
BUNDLE=".build/vphone-cli.app"
BUNDLE_BIN="${BUNDLE}/Contents/MacOS/vphone-cli"
BUNDLE_VM="${BUNDLE}/Contents/MacOS/vphone-vm"
BUNDLE_ARCHIVE="${BUNDLE}/Contents/MacOS/vphone-archive"
+BUNDLE_ASKPASS="${BUNDLE}/Contents/MacOS/vphone-ask-for-permission"
+BUNDLE_AMFI="${BUNDLE}/Contents/MacOS/vphone-amfi-allow"
INFO_PLIST="sources/Info.plist"
ENTITLEMENTS="sources/vphone.entitlements"
BUILD_INFO="sources/VPhoneCore/VPhoneBuildInfo.swift"
@@ -51,6 +60,22 @@ echo '// Auto-generated — do not edit' > "$BUILD_INFO"
echo "enum VPhoneBuildInfo { static let commitHash = \"${GIT_HASH}\" }" >> "$BUILD_INFO"
swift build -c release
+# vphone-amfi-allow, which SwiftPM cannot produce: it reads amfid's ObjC runtime
+# and so must match amfid's own slice, which is arm64e. Plain clang, two system
+# frameworks, no Xcode.app and nothing on PATH beyond the toolchain that just
+# built everything else.
+echo "=== Building vphone-amfi-allow (arm64e) ==="
+clang -arch arm64e -O2 \
+ -framework CoreFoundation -framework Security \
+ -o "$AMFI_BINARY" "$AMFI_SOURCE"
+# An arm64 build would compile and link and then fail at run time with nothing
+# to say, because task_for_pid on an arm64e amfid from an arm64 tool cannot read
+# the pointer-authenticated slot it is looking for. Assert the slice.
+if ! file "$AMFI_BINARY" | grep -q arm64e; then
+ echo "Error: ${AMFI_BINARY} is not arm64e." >&2
+ exit 1
+fi
+
# Only vphone-vm gets the entitlements. Signing vphone-cli with them too would
# put us straight back where we started: the entry point itself unable to
# launch without an AMFI bypass already in place.
@@ -58,7 +83,10 @@ echo "=== Signing ==="
codesign --force --sign - --entitlements "$ENTITLEMENTS" "$VM_BINARY"
codesign --force --sign - "$BINARY"
codesign --force --sign - "$ARCHIVE_BINARY"
-echo " signed: vphone-vm (entitled), vphone-cli, vphone-archive"
+codesign --force --sign - "$ASKPASS_BINARY"
+codesign --force --sign - "$AMFI_BINARY"
+echo " signed: vphone-vm (entitled), vphone-cli, vphone-archive,"
+echo " vphone-ask-for-permission, vphone-amfi-allow"
# An unentitled vphone-vm is worse than a broken one: it launches perfectly,
# which convinces vphone-cli's AMFI probe that nothing is wrong, and only fails
@@ -81,6 +109,8 @@ mkdir -p "${BUNDLE}/Contents/MacOS" "${BUNDLE}/Contents/Resources"
cp -f "$BINARY" "$BUNDLE_BIN"
cp -f "$VM_BINARY" "$BUNDLE_VM"
cp -f "$ARCHIVE_BINARY" "$BUNDLE_ARCHIVE"
+cp -f "$ASKPASS_BINARY" "$BUNDLE_ASKPASS"
+cp -f "$AMFI_BINARY" "$BUNDLE_AMFI"
cp -f "$INFO_PLIST" "${BUNDLE}/Contents/Info.plist"
cp -f "sources/AppIcon.icns" "${BUNDLE}/Contents/Resources/AppIcon.icns"
cp -f "scripts/vphoned/signcert.p12" "${BUNDLE}/Contents/Resources/signcert.p12"
@@ -100,6 +130,8 @@ rm -f "${BUNDLE}/Contents/MacOS/ldid" "${BUNDLE}/Contents/MacOS/vphone-letmein"
# and `codesign -v` on the bundle reports "nested code is modified or invalid".
codesign --force --sign - "$BUNDLE_BIN"
codesign --force --sign - "$BUNDLE_ARCHIVE"
+codesign --force --sign - "$BUNDLE_ASKPASS"
+codesign --force --sign - "$BUNDLE_AMFI"
codesign --force --sign - --entitlements "$ENTITLEMENTS" "$BUNDLE_VM"
echo " bundled → ${BUNDLE}"
@@ -171,6 +203,8 @@ echo "=== Re-signing bundled binaries (resealing Resources) ==="
# Nested first, main executable last — see the bundling step above.
codesign --force --sign - "$BUNDLE_BIN"
codesign --force --sign - "$BUNDLE_ARCHIVE"
+codesign --force --sign - "$BUNDLE_ASKPASS"
+codesign --force --sign - "$BUNDLE_AMFI"
codesign --force --sign - --entitlements "$ENTITLEMENTS" "$BUNDLE_VM"
codesign -v "$BUNDLE_VM" \
|| { echo "Error: the bundle seal did not verify after signing." >&2; exit 1; }
@@ -178,12 +212,15 @@ echo " resealed OK"
echo ""
echo "=== Build complete ==="
-echo " vphone-cli : ${BINARY} (no entitlements — always launches)"
-echo " vphone-vm : ${VM_BINARY} (entitled — amfid may refuse it)"
-echo " vphone-archive : ${ARCHIVE_BINARY}"
-echo " bundle : ${BUNDLE}"
-[[ "$BUILD_VPHONED" -eq 1 ]] && echo " vphoned : .build/vphoned.signed"
+echo " vphone-cli : ${BINARY} (no entitlements — always launches)"
+echo " vphone-vm : ${VM_BINARY} (entitled — amfid may refuse it)"
+echo " vphone-archive : ${ARCHIVE_BINARY}"
+echo " vphone-ask-for-permission : ${ASKPASS_BINARY}"
+echo " vphone-amfi-allow : ${AMFI_BINARY} (arm64e)"
+echo " bundle : ${BUNDLE}"
+[[ "$BUILD_VPHONED" -eq 1 ]] && echo " vphoned : .build/vphoned.signed"
echo ""
echo "Run: ${BINARY} --help"
-echo "If vphone-vm is killed the moment it launches, amfid refused its entitlements;"
-echo "'make amfi_command' prints the bypass command line for these exact binaries."
+echo "If vphone-vm is killed the moment it launches, amfid refused its entitlements."
+echo "'make amfi_allow' allows this build past it; re-run it after every build,"
+echo "because it allowlists cdhashes and those change with every signature."
diff --git a/scripts/check_aux.sh b/scripts/check_aux.sh
index c8e759f9..6360e280 100755
--- a/scripts/check_aux.sh
+++ b/scripts/check_aux.sh
@@ -70,14 +70,16 @@ typeset -a REGISTERED_REMAINING=(
# reporting it. `is_registered` still folds python3.13 and friends onto
# `python3`, so a versioned lookup fails under the name people will search for.
#
-# The AMFI bypass is deliberately NOT on that list and must never be added to
-# it. Whatever program lets amfid accept vphone-vm's entitlements — amfidont or
-# anything else — is the user's, run by hand from their own shell. Nothing here
-# installs it, spawns it, or looks for it on PATH, so it is not a dependency of
-# this bundle and its absence is not a debt to pay down; `make amfi_command`
-# only prints a command line for the user to run. If a script ever does reach
-# for one, gate 2 below should fail: that would be the project taking on the
-# dependency, which is exactly what it stopped doing.
+# The AMFI bypass is not on that list either, and for the opposite reason to
+# the one that used to be written here: it is not an external program any more.
+# `vphone-amfi-allow` is built from this repository's own C, ships in the
+# bundle, and links CoreFoundation, Security and libSystem — so gate 1 weighs it
+# like everything else rather than it being someone else's problem. It was
+# `amfidont`, installed by the user into the user's own Python, back when the
+# honest thing to say was that the bypass was theirs and not ours.
+#
+# What still must not appear is a LOOKUP: `make amfi_allow` runs the binary by
+# absolute path, and any `command -v` for an AMFI tool is gate 2's business.
# Programs macOS ships that we depend on and intend to keep. This is the
# honest boundary of "zero dependencies" — widening it means editing this file,
@@ -242,9 +244,7 @@ check_sources() {
#
# Two things are not interpreter use here. Comment lines: the repo explains
# what the Python used to do in a lot of places, and that history is worth
- # keeping. And `echo`/`print` lines: `make amfi_command` prints the command
- # that installs amfidont, which is the USER's tool, in the USER's own python,
- # run from the USER's own shell — nothing here installs or spawns it.
+ # keeping. And `echo`/`print` lines, which name a command without running it.
#
# check_aux.sh excludes itself, because a scanner that looks for a word
# necessarily contains it.
diff --git a/sources/vphone-ask-for-permission/VPhoneSudo.swift b/sources/VPhoneCore/VPhoneSudo.swift
similarity index 100%
rename from sources/vphone-ask-for-permission/VPhoneSudo.swift
rename to sources/VPhoneCore/VPhoneSudo.swift