Sig handling version bump - #115
Merged
Merged
Conversation
Updates the host verifier to spacedb 0.1.4 (verifier-side hardening and a path.rs panic fix; no change to the merkle hashing or root computation). The workspace requirement stays "0.1", so only the workspace Cargo.lock moves. The ZK guest keeps its own pinned lock (methods/guest/Cargo.lock at 0.1.2) and veritas verifies against the committed ELFs + hardcoded image IDs, so the guest ELF and image IDs are unchanged.
Record sets whose embedded signature does not verify are now silently
dropped from the verified Zone rather than failing the whole message. This
is permissive toward e.g. records left behind by a rotated key, while
preserving the invariant that everything in Zone::records is authentically
owner-signed. Applies to owner, delegate, temporary-handle, and
final-handle record sets.
The omission is surfaced through inspect (not by injecting a synthetic
record, which would break the signed-only invariant and be spoofable):
record_summary now re-runs verify_records against the same signer key the
verifier resolves and reports the result as SigStatus::{Valid,Invalid,
Unchecked} on RecordSummary.
The generated JS error only put the `{msg}` detail in `.inner.msg`; its
`.message` (and thus `toString()`/`${e}`) was just
"VeritasError.VerificationFailed", so consumers logging `${e}` lost the
detail.
Marking the error `#[uniffi(flat_error)]` lowers the Display string over
the FFI, which ubrn's flat-error template feeds into the error's
`.message`. Variant discrimination via `.tag` is preserved; the detail
now travels in `.message` instead of `.inner.msg`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.