The Churts
Page 2 of 6 · newest first · back to latest
uBixCore — Thirteen Tags in Four Days, and the Rule That Made It Safe
uBixCore went from v0.21 to v0.33 in four days. None of it was planned in advance — every tag exists because Sowing.me ran into something it couldn't do. That's a good way to build a framework and a fast way to ruin one, and the difference is a single question I ask before anything goes upstream.
uBixVault 1.3 — The Token That Could Mint Root, and Signing In Properly
1.3 fixes a critical hole in token creation — a token allowed only to create tokens could create a root one — caps how long any token can keep itself alive, and lets the web console sign in with a username and password or LDAP. If anything in your policies grants auth/token/create, upgrade.
uBixVault 1.4 — Vault-Compatible, Checked With Vault's Own Client
uBixVault has always said it speaks a Vault-compatible API. In 1.4 I finally tested that claim with HashiCorp's own Go client — the one the vault CLI and External Secrets Operator are built on. It failed on the very first call. Now it doesn't, and along the way the testing turned up policies stored empty, LDAP forced into insecure TLS, and 80,000 forgotten tokens.
uBix Vault 1.2 — High Availability, Because Nodes Get Drained
1.2 runs uBix Vault as several replicas: one active, the rest standing by, all behind one Service. A node drain or a rolling upgrade now hands over in about half a second without a failed request — and a replica that loses the lock without noticing can't write a thing.
uBixCore 0.17 — Real-Time Publishing Without a Client Library
PHP-FPM can't hold a WebSocket, and a message posted to one pod can't reach a socket held by another. uBixCore 0.17 adds the framework half of the fix: a NATS publisher that speaks the protocol itself, and signed subject grants a gateway in any language can verify.
uBix Vault 1.1 — The First Enterprise-Parity Feature: Resource Quotas
1.0 matched HashiCorp Vault's free tier. 1.1 is the first step toward the *Enterprise* feature set — resource quotas: rate-limit quotas and lease-count quotas, in-house, over the Vault-compatible API. Additive, backward-compatible, and built design-first.
uBix Vault 1.0 — Stable, and Honest About What That Means
uBix Vault is 1.0. That is a promise about the interface, not a claim that the crypto has been audited — and I want to be exact about the difference, because for a secrets manager the difference is the whole point.
uBixCore 0.2 — From Monorepo to Framework, Skeleton, and Runtime
uBixCore used to be a monorepo you forked. As of 0.2 it is a framework you install: a Composer package, a create-project skeleton, and a public PHP runtime image, all under github.com/ubixsys. Here is what changed, why the product had to move out first, and what stands between 0.2 and 1.0.