keysink 0.1.3 → 0.1.5

package/README.md

@@ -47,6 +47,9 @@ everything in its environment — but the real key was never in there.
    cargo install keysink      # from crates.io, needs a Rust toolchain
    ```
 
+   `cargo install` lands in `~/.cargo/bin`, which sudo can't see. So if you later
+   run `sudo keysink deploy`, use `sudo ~/.cargo/bin/keysink deploy`.
+
    Prebuilt binaries are also on
    [Releases](https://github.com/wusende/keysink/releases) — Linux / macOS /
    Windows, amd64 / arm64 — put one on your `PATH`. The npm package is a thin
@@ -108,7 +111,7 @@ talk to two different providers, or to the same provider with different keys.
 ```
 keysink init                     # first entry point in scripts / headless environments (interactive serve auto-initializes)
 keysink route add|ls|show|rotate|update|rm|enable|disable
-keysink serve [--listen 127.0.0.1:8787] [--audit-log FILE] [--max-concurrent N]
+keysink serve [--listen 127.0.0.1:8787] [--audit-log FILE] [--max-concurrent N] [--accept-degraded]
 keysink status | doctor
 keysink export --output FILE      # needs master password; strips all key values
 keysink rekey [--yes]             # rotate the vault master key
@@ -152,8 +155,9 @@ a terminal, init manually:
 runuser -u keysink -- /usr/local/bin/keysink --home /var/lib/keysink init
 ```
 
-Admin commands then go through `sudo -u keysink keysink …`; each invocation
-re-authenticates (`timestamp_timeout=0`), so an agent cannot silently run them.
+Admin commands then go through `sudo -u keysink /usr/local/bin/keysink …`; each
+invocation re-authenticates (`timestamp_timeout=0`), so an agent cannot silently
+run them.
 
 ## Security model
 
@@ -172,13 +176,17 @@ that can read both `vault.key` and `vault.age` can still decrypt offline —
 machine-level isolation stays your job (tight sudo, separate UID).
 
 `--audit-log` records route, vkey fingerprint, status and latency — never
-headers, body or query. Off by default.
+headers, body or query. Off by default. Five rotated generations (10 MB each)
+are kept, and rejected requests are admitted at 1/s per fingerprint — a flood
+of unauthenticated requests cannot rotate the forensic trail away.
 
 `--listen` will bind a non-loopback address if you insist, but then TLS and
 network exposure are yours to solve; the intended deployment is loopback only.
 Everything a request touches is bounded by default — body size, in-flight
 requests, connections, time — so a hung upstream or a misbehaving agent can't
-take the gateway down.
+take the gateway down. Idle connections are bounded too: http1 heads must
+finish within 30s, and h2 connections that stop answering keep-alive PINGs
+are closed.
 
 ## What this is not
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "keysink",
-  "version": "0.1.3",
+  "version": "0.1.5",
   "description": "Local gateway that keeps real AI API keys out of agents (Claude Code, OpenAI, MCP): agents hold revocable virtual keys, real keys stay in an encrypted vault.",
   "license": "MIT",
   "author": "wusende",