A fix release for spinuptui ssh-exec, the command that lets an agent run diagnostics on a server without being able to change it. Its read-only guard let Redis writes and many WP-CLI writes through. Both are closed, and the update command now reliably fetches the newest version.
Fixed
- Redis writes are denied. The guard had no rules for Redis, so
redis-cli CONFIG SET …,FLUSHALL,FLUSHDB,BGSAVEand plainSET/DELran as if they were diagnostics.redis-cliis now allowed only with a known read:ping,info,dbsize,lastsave,config get,memory doctor|stats|usage,latency latest|history,slowlog get|len,client list|infoand a few key-inspection reads. Everything else is denied, including unrecognised options and a bareredis-clifed from stdin. - Unlisted WP-CLI writes are denied. The guard named a dozen WP-CLI writes and allowed every other command, so
wp transient delete,wp search-replace,wp eval,wp plugin uninstallandwp cron event rungot through.wpis now allowed only with a known read (plugin list,option get,core version,cache type,cron event list,db sizeand the like), and--exec,--require,--sshand--httpare refused on any command. - Denials say what was refused. The message names the verb or option, for example
redis-cli `config set` is not on the read-only allowlist. - The update command now actually updates. The About panel (
?) suggestsbun add -g spinuptui@latest --no-cache. Without--no-cache, Bun can resolve@latestfrom a cached copy of the package listing and reinstall the version you already have.
Changed
wp user list,wp user getandwp user list-capsare allowed. The guard used to refuse everything underwp user, reads included. Creating, deleting and changing users is still denied.
Notes
- Two reads that used to pass are now denied:
wp config getandwp config list, because they print the database password into the audit log. - A WP-CLI read that isn't on the list is denied too, where it used to pass. If a diagnostic you rely on is refused, open an issue and it can be added.
- The guard still isn't a sandbox. Outside
redis-cliandwpit matches known-destructive patterns, so it catches mistakes, not a determined write.