Repository navigation
Releases
Vafa 1.0.9
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.
Vafa 1.0.8
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.8.dmg | brew install --cask k33ssa/tap/vafa, or open the DMG and run sudo ./install.sh |
| Windows 10/11 | Vafa-1.0.8-windows.zip | Unzip, double-click install.cmd, allow the UAC prompt |
Changed (macOS) — please update from 1.0.7
- 1.0.7 stopped false connection drops, but to do so it trusted the last known exit country for up to 12 s when a country check was slow. If the VPN client silently switched to another server on the same tunnel at that moment, the change could go unnoticed for that long. 1.0.8 restores the strict 3 s limit.
- Country checks are now independent requests: a new one every second while there is no answer, each on its own connection, rotating between three addresses. A single slow request no longer matters (the next one answers), so connections are not cut for nothing; if no request answers for 3 s, the network is closed as before.
- After a network event, answers of requests started before it are discarded.
- The log now says why the exit country is unconfirmed (network event or no answer), and reports any guard cycle longer than 2 s.
Update: brew upgrade --cask vafa (or brew install --cask k33ssa/tap/vafa if not installed yet).
Windows: no changes since 1.0.3.
Vafa 1.0.7
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.7.dmg | brew install --cask k33ssa/tap/vafa, or open the DMG and run sudo ./install.sh |
| Windows 10/11 | Vafa-1.0.7-windows.zip | Unzip, double-click install.cmd, allow the UAC prompt |
Fixed (macOS) — hotfix, please update
- Connections to the protected service dropped roughly every 1.5 minutes (since 1.0.1). macOS (
wifip2pd: AirDrop, Handoff, Universal Control, AirPlay) keeps adding and removing routes onawdl0/llw0even with AirDrop turned off; the guard took this for a network change, closed the network, re-checked the exit country and cut open connections. These routes are now ignored; real tunnel events (VPN reconnect) are handled as before. - A single slow exit-country answer (over 3 s) through a working tunnel also cut connections. Without a network event, on the same tunnel, the last answer is now trusted for up to 12 s, as before 1.0.1.
Update: brew upgrade --cask vafa (or brew install --cask k33ssa/tap/vafa if not installed yet).
Windows: no changes since 1.0.3.
Vafa 1.0.6
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.6.dmg | brew install --cask k33ssa/tap/vafa, or open the DMG and run sudo ./install.sh |
| Windows 10/11 | Vafa-1.0.6-windows.zip | Unzip, double-click install.cmd, allow the UAC prompt |
Fixed (macOS installer)
- Installing through Homebrew (or from a downloaded DMG) could stop with
Bootstrap failed: 5: Input/output errorand the guard daemon did not start. The real cause: downloaded files carry thecom.apple.quarantinemark, the installer copied it onto the daemon and its launchd plist, and recent macOS versions refuse to load a quarantined service ("Refusing to execute/trust quarantined program/file"). The installer now removes the quarantine mark from the daemon files it installs.
If an earlier install stopped with this error: brew reinstall --cask k33ssa/tap/vafa.
Windows: no changes since 1.0.3.
Vafa 1.0.5
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.5.dmg | brew install --cask k33ssa/tap/vafa, or open the DMG and run sudo ./install.sh |
| Windows 10/11 | Vafa-1.0.5-windows.zip | Unzip, double-click install.cmd, allow the UAC prompt |
Fixed (macOS installer)
- Installing over an existing Vafa could fail with
Bootstrap failed: 5: Input/output error: the installer started the new daemon while the old one was still stopping, then aborted before copying the menu bar app, so no shield appeared. The installer now waits for the old daemon to unload, retries starting the new one, and always installs the menu bar app.
If an earlier install stopped with this error, run brew reinstall --cask k33ssa/tap/vafa (or open the DMG and run sudo ./install.sh).
Windows: no changes since 1.0.3.
Vafa 1.0.4
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.4.dmg | brew install --cask k33ssa/tap/vafa, or open the DMG and run sudo ./install.sh |
| Windows 10/11 | Vafa-1.0.4-windows.zip | Unzip, double-click install.cmd, allow the UAC prompt |
What's new (macOS menu bar shield)
- The shield app is now signed with a stable local signing identity instead of an ad-hoc signature. With ad-hoc signing every build had a new code identity, and macOS 26 keeps the "Allow in the Menu Bar" list and the icon position per identity, so after an update the icon could disappear. From this version on the identity stays the same between updates (after this update macOS may list Vafa once more as a new entry).
- On macOS 26, if the system does not let the shield into the menu bar, Vafa shows a one-time hint: System Settings → Menu Bar → "Allow in the Menu Bar".
Windows: no changes since 1.0.3.
Updating
macOS: brew upgrade --cask vafa, or open the DMG and run sudo ./install.sh. The protection stays on during the update.
Vafa 1.0.3
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.3.dmg | brew install --cask k33ssa/tap/vafa, or open the DMG and run sudo ./install.sh |
| Windows 10/11 | Vafa-1.0.3-windows.zip | Unzip, double-click install.cmd, allow the UAC prompt |
What's new (Windows)
- The tray shield now shows the real state for a regular (non-elevated) user. Before, it could not see the guard's system task and showed "guard off" (empty shield) while the block was actually working.
- The shield pins itself to the taskbar once on first start, so it no longer hides under the ^ arrow. If you hide it later, it stays hidden.
- Turning the guard off writes the "stopped" state, so the tray switches to "guard off" right away.
Checked live on Windows 11 (26H2, ARM): install from this release, tray state, and a reboot without VPN — the firewall rule blocks the protected addresses from boot, before the service starts.
Updating
macOS: nothing changed since 1.0.2. Windows: download the new zip and run install.cmd again (settings are kept).
Vafa 1.0.2
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.2.dmg | brew install --cask k33ssa/tap/vafa, or open the DMG and run sudo ./install.sh |
| Windows 10/11 | Vafa-1.0.2-windows.zip | Unzip, double-click install.cmd, allow the UAC prompt |
What's new
- When the VPN drops, apps are frozen right away. Previously the daemon first closed every already open connection to the protected addresses one by one (about 95 calls, up to 4 s under load) and only then froze the apps. Now connections are cut in parallel and freezing does not wait for it. The network rule itself still applies instantly.
Updating
From 1.0.1 — brew upgrade --cask vafa keeps the protection on during the update. From 1.0.0 — update with the VPN on, or open the DMG and run sudo ./install.sh.
Vafa 1.0.1
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.1.dmg | brew install --cask k33ssa/tap/vafa, or open the DMG and run sudo ./install.sh |
| Windows 10/11 | Vafa-1.0.1-windows.zip | Unzip, double-click install.cmd, allow the UAC prompt |
What's new
- The AI coding CLI is frozen too when the VPN is down (all copies, found by code signature, together with the commands it started); launching it is blocked.
- Copies of a protected app in another folder are caught by code signature.
- VPN clients in system-proxy mode (xray, sing-box, Clash…) are supported on macOS.
- The exit-country check runs in the background: a stalled tunnel no longer delays freezing.
- The menu bar shield shows up on macOS 26.
- Updating through Homebrew no longer lifts the protection: the old version stops with the network closed and apps frozen, the new one takes over.
Updating from 1.0.0
Homebrew removes 1.0.0 with its own (old) uninstall step, which lifts the protection for a few seconds. Update with the VPN on, or open the DMG and run sudo ./install.sh — that path keeps the protection on. Updates after 1.0.1 are safe.
Vafa 1.0.0
Vafa (Verify access for apps) blocks selected apps and their network access until a VPN with an allowed exit country is up. Without VPN the apps are frozen and cannot launch; when VPN returns they unfreeze automatically. A shield in the menu bar / tray shows the status.
Downloads
| Platform | File | Install |
|---|---|---|
| macOS 12+ (Apple Silicon + Intel) | Vafa-1.0.0.dmg | brew install --cask k33ssa/tap/vafa, or open the DMG and run sudo ./install.sh |
| Windows 10/11 | Vafa-1.0.0-windows.zip | Unzip, double-click install.cmd, allow the UAC prompt |
Update: macOS — brew upgrade --cask vafa; Windows — download the new zip and run install.cmd again (settings are kept).