Repository navigation
blackice 1.1.0
Immutable
release. Only release title and notes can be modified.
Fixed:
- A daemon that registers gets the events still waiting for an answer. An event raised while no daemon was
registered (event_not_sent no_daemon), in the 10 s launchd takes to start one again after an upgrade, astart
or a SIGTERM, was never sent, and one whose hook ended with its daemon had nothing left to answer it: either
waited for its deadline and was dropped. On 15 November, on 1.0.8, two connections of Discord's helper raised in
the 10 s after astartwere dropped that way, and so was acurlwhose hook a SIGTERM stopped. The extension
now sends the new daemon every pending event that is not past its deadline and whose token no answer has
presented (control events_sent_again), and the daemon runs their hooks with the time they have left. An event
that reaches the daemon twice, raised while it registers and so sent both on its own and again, runs its hooks
once (hooks_skipped,already_received). blackice startloads the daemon again when it finishes an upgrade and launchd no longer has it.brew upgrade
boots the daemon out and deletes its LaunchAgent, since Homebrew runs the cask'suninstall launchctl:on an
upgrade too, andstartleft it so: it said "blackice is on in ask mode, fx answers" while no hook ran, and only
blackice statussaid the daemon was not running. On 16 November, afterbrew upgradefrom 1.0.7 to 1.0.8 and
start, three events were not sent (event_not_sent no_daemon). A start that upgrades nothing leaves a daemon
that is not loaded as it is, sinceblackice agent uninstallis how you stop the hooks, and says in ask mode
that the hooks need it, asblackice modedoes.blackice stopandstartsay where to run them when macOS needs an administrator to confirm and cannot ask.
Over ssh macOS's dialog does not show, and the command ended with macOS's words alone (OSSystemExtensionErrorDomain 13); it now adds that the command has to run in a terminal on the Mac itself.