• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

LFDT-Panurus / panurus / 35208333042
85%

Build:
DEFAULT BRANCH: main
Ran 17 Sep 2026 10:12AM UTC
Jobs 0
Files 0
Run time –
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

pending completion
35208333042

push

github

Effi-S
feat(storage): verify integrity of high-value stored payloads

The store services persisted whatever they were handed. Nothing in their
API stated whether the bytes had been cryptographically verified, and
nothing re-checked them on the way out, so a wrong row, a truncated blob
or a cross-transaction payload was indistinguishable from authentic
evidence.

Add a small `token/services/storage/integrity` package with typed
sentinel errors and wire it into the paths where a stored payload becomes
a claim someone acts on:

- Token requests are refused at insert if the transaction id, the request
  bytes or the public parameters hash are empty. On retrieval,
  `ttxdb`/`auditdb` deserialise the stored payload and require its anchor
  to equal the transaction id it is filed under. `endorserdb` holds the
  bare actions format, which carries no anchor, so it gets a version and
  non-empty-actions check instead. A zero-length token request is treated
  as not-found rather than as an integrity failure, so the guard is
  independent of how a driver scans an empty request column.
- Public parameters are addressed by their hash, so `PublicParamsByHash`
  now recomputes that hash over what it is about to return and refuses a
  mismatch. These carry the issuer and auditor keys and the setup every
  action is validated against. `StorePublicParams` propagates that
  mismatch instead of surfacing it as a primary-key violation from the
  fall-through INSERT.
- Empty identities are refused, and identity lookups compare the stored
  identity against the requested one. This matters because an empty
  identity's unique id is the constant "<empty>", so every empty identity
  collides on one row and one cache key. Applied to both the SQL and KVS
  backends; `GetExistingSignerInfo` and `SignerInfoExists` no longer
  consult the shared "<empty>" key.
- Endorsement acknowledgements are refused at insert if the endorser or
  the signature is empty. A vacuous row read back is logged... (continued)
Source Files on build 35208333042
Detailed source file information is not available for this build.
  • Back to Repo
  • Github Actions Build #35208333042
  • 03cc95a0 on github
  • Prev Build on main (#35196652316)
  • Next Build on main (#35308968538)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc