Repository navigation
Vafa (Verify access for apps) blocks selected apps and their network access until a VPN with an allowed exit country is up.
Downloads
| Platform | File | Install |
|---|---|---|
| macOS 12+ (Apple Silicon + Intel) | Vafa-1.0.9.dmg | brew install --cask k33ssa/tap/vafa, or open the DMG and run sudo ./install.sh |
| Windows 10/11 | Vafa-1.0.9-windows.zip | Unzip, double-click install.cmd, allow the UAC prompt |
Fixed (macOS) — hotfix, please update
- Connections were cut when the Mac was overloaded (for example while an emulator or simulator was starting). The guard itself stalled for 5–10 s on slow
psandcodesigncalls, then counted its own stall as "no answer about the exit country" and closed the network. These calls now run in the background and the guard loop never waits for them longer than 0.15 s. - After a stall of the guard (overload, sleep) the exit country is re-checked first: new connections are held, open ones are kept; they are cut only if the re-check fails or gets no answer within 3 s.
Added (macOS)
- Boot lock: firewall rules do not survive a reboot on macOS, so a tiny separate startup task now closes the protected addresses at boot without waiting for the main guard. Only the guard can open the network again, once it has confirmed the VPN and its exit country. Turning the guard off or uninstalling removes the lock.
- The log reports any guard cycle longer than 2 s, step by step.
Update: brew upgrade --cask vafa (or brew install --cask k33ssa/tap/vafa if not installed yet).
Windows: no changes since 1.0.3.