Repository navigation
Releases: roypadina/VaultBar
Release list
v0.2.5
SHA-256: ca1bf00c626e5cb892f4391de72a96017a4dbed089eb643d277af606ade90c4d
Releases are now signed with a stable identity, so permissions survive future updates. After this one update you may need to re-allow any macOS permission prompts once.
v0.2.4
VaultBar 0.2.3
SHA-256: 966b574fc14dc60437e4460f0f55da320675122a331c155ec303e5bccc3da823
Universal build: now runs on Intel Macs as well as Apple Silicon. README polish: selling points, honest comparison with Cryptomator and VeraCrypt, screenshots, Open Anyway steps for macOS 15+.
VaultBar 0.2.2
SHA-256: ee30b82a06943220fda2c71476f18382d4ab7045288fc089ed376952b05dfd85
--unregister-login-itemnever mistakes "unknown" for "nothing to lock": an unreadable config or a failinghdiutil infonow exits 1 and changes nothing, instead of removing the login item (which stops a running copy that may hold unlocked vaults).- README: unregister locks what it can; any vault that can't be locked keeps the login item;
--forceforce-locks busy ones.
Upgrade: brew upgrade --cask roypadina/tap/vaultbar (0.2.1+ hands over with no gap).
VaultBar 0.2.1
SHA-256: 52cc5a189256bb435300f44fcc85528f47884789a2c7481659519cdf4a36cfea
- Always exactly one copy running, never zero (from 0.2.1 on): the login item is now a classic LaunchAgent (
~/Library/LaunchAgents/com.padina.vaultbar.login.plist). The old SMAppService agent pinned the binary and broke after Homebrew upgrades (EX_CONFIG / "needs LWCR update"). Hand-offs and upgrades use an ack protocol: the old copy quits only after the new one confirms. Measured 0 ms gaps in a launchd test harness. - Unlock prompt shows and switches the mode: " — Read & Write" / "— Read-Only", a mode switch, ⌘R toggles.
- Control-click on the menu bar icon opens the menu (was: unlock prompt).
vaultbar --unregister-login-item [--force]locks every vault before removing the login item.
Upgrading from 0.2.0 or older may leave VaultBar stopped for 1–2 s once; later upgrades are gap-free.
VaultBar 0.2.0
SHA-256: 5bde575d06afefe791fdb7389be5e55522a6b69f207ad5790a1767d6b401a148
New:
- Private mount: per-vault mount folder (created on unlock, removed on lock or any eject), optionally hidden from Finder.
- Read-only unlock: per-vault default, ⌥ "Unlock Read-Only…",
?readonly=1, CLI--readonly. vaultbarCLI:status [--json],path,lock,unlock [--readonly] [--wait s],open. No password path; exit codes 0/1/2/3/64.- Notifications + history: generic notifications for auto-locks, a pre-force warning with "Keep unlocked 15 min", failed locks; last 50 events in memory.
- Panic lock: global hotkey (default ⌃⌥⌘L, forces), ⌥-click = Lock All,
vaultbar://lockall. - Change password via
diskutil image chpass(re-wraps the key; see Security model). - Prompt: Caps Lock and keyboard-layout hints, VoiceOver announcement and labels.
Fixes: hand-off race with the login agent, relaunch fallback when the app is moved.
Upgrade: brew upgrade --cask roypadina/tap/vaultbar (0.1.3+ restarts on the new version by itself).
VaultBar 0.1.3
SHA-256: efae0ae08c03f9a82bc282a3295799c8d9e50ef604f80e29eb077fe4923c7f7c
Fixes the login agent breaking after a Homebrew upgrade (launchd: "Could not find and/or execute program", exit 78).
- On every launch outside launchd, VaultBar re-registers its login agent from its own bundle.
- Hand-off to the agent now verifies a VaultBar process is running, else keeps an unsupervised copy (never ends up not running).
- Upgrades are detected automatically: within ~30 s of
brew upgrade(once idle) the running copy restarts on the new version.
Upgrading from 0.1.2 or older: after brew upgrade --cask roypadina/tap/vaultbar, quit VaultBar from its menu and open it once.
VaultBar 0.1.2
SHA-256: 391d42ff9c3c4683a52452018503531c3e0beb257e5009b4c1abcfec49a00346
- Open vaults in Finder: menu "Open in Finder" / "Unlock & Open…",
vaultbar://open/<name>, and a Raycast "Open " script (unlocks first if needed). - New setting "Open in Finder after unlocking" (off by default).
- Raycast scripts are synced on every launch.
- A copy started from Finder or
openhands over to the supervised login agent once idle, so crash restart works right away. - Docs: URL action table, slug naming.
Upgrade: brew upgrade --cask roypadina/tap/vaultbar.
VaultBar 0.1.1
SHA-256: b76a7204118fca4a49a0b0b1c404450b8f6bda86769a175853c298047803fb6c
- Always running: the login item is now a LaunchAgent that restarts VaultBar if it crashes (not after a deliberate Quit). Single-instance guard.
- Quit while a vault is unlocked asks: Lock All & Quit / Quit / Cancel.
- Password prompt is focused and ready to type from a click, the menu, a vaultbar:// link or Raycast.
- Unlocked state is now an amber open padlock in the menu bar; paused shows an orange warning badge.
- Icon metadata stripped.
Upgrade: brew upgrade --cask roypadina/tap/vaultbar.
VaultBar 0.1.0
SHA-256: 20b6fb517854f9c4f6d3044f6c0e1eca2f8ded16dd8bee0c0d95c770146fef6b
First release.
- Lock/unlock encrypted APFS sparse-bundle vaults from the menu bar (left-click = default vault, right-click = menu).
- Password popup; the password goes to hdiutil on stdin only and is never stored.
- Auto-lock on sleep, screen lock and idle, with a 1-hour pause.
- Multiple vaults, New Vault…, Add Existing Vault…, URL scheme, optional Raycast script commands.
Install: brew install --cask roypadina/tap/vaultbar. Ad hoc signed (not notarized): if macOS blocks the first launch, run xattr -dr com.apple.quarantine /Applications/VaultBar.app.