dfe34a6032122a5ba98b71cff35a36556964376b
UpdateBinding documents that an empty caller Secret is preserved by COALESCE(NULLIF(?, ''), secret), and binding.ValidateForUpdate explicitly makes an empty Secret mean "keep the current one". The sentinel was defeated before the SQL saw it: encryptBindingSecret ran first and, with a binding cipher configured, sealed the empty string into a non-empty "arcie-binding:v1:<fp>:<base64>" envelope. NULLIF(?, '') then no longer matched, COALESCE took the envelope, and a routine PATCH that changed only name/source/ workflow overwrote the shared HMAC secret with the encrypted empty value. Once re-approved the binding could never authenticate an inbound webhook again, and nothing surfaced the loss. Fix it at the producer rather than by re-testing emptiness at the SQL layer: an empty secret is the store's "no secret" sentinel, so it stays empty and the existing COALESCE guard keeps working. decryptBindingSecret already treats an empty stored value as nothing-to-decrypt, so this is symmetric. The only existing coverage, TestUpdateBindingPreservesSecretWhenEmpty, opens the store without a cipher and so never exercised this path. Add a table-driven test over the cipher path covering both directions -- an empty caller secret must preserve the stored secret, and a supplied one must still replace it, so the fix cannot degrade into "updates never change the secret". Found by an adversarial package sweep (temp tracker: persistence-1, .local/issue-tracker/).
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.8%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%