You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Aggregate per-connection byte budget for structural objects on a writable listener #233
Spotted in the #227 review. Object::blob_size returns 0 for trees, snapshots, secrets and transcripts, so a writable sc serve connection has no aggregate byte bound on repeated PutObject of distinct structural objects. Each is individually capped by the max object size, but nothing bounds the sum per connection; the bound today is --max-connections x connection lifetime (--timeout).
This predates #227 (it was already true at the old fixed 256 MiB cap), but a raised --max-object-size (up to 1 GiB) amplifies it.
Proposal: a per-connection running byte budget on object-write verbs (PutObject, PutPack ingest) in the serve loop, with a typed refusal and a flag (or reuse of --max-pack-size semantics), mirroring the PutPack spool cap.
Until then (documented in THREAT-MODEL.md and ADR-0039): prefer read-only or token-gated listeners, keep --max-object-size low, and size --max-connections down.
Activity
fix(repo): chunk size fits the smallest valid receiver, early cap che…
feat(core,repo,cli): operator-configurable max object size (#227)
fix(repo): charge pack structural bytes on ingest errors, keep serve_…
fix(repo,cli): charge a pack max(spool, decoded) bytes, budget bucket…
test(repo): cover the spool half of the pack charge; tidy client reco…
fix(repo,cli): charge over-cap PutObject attempts, warn for --max-pac…
feat(repo,cli): per-connection write budget on sc serve (--max-conn-b…