Home / Docs / Diagnostics
U7010: A package, archive, statement, root, checkpoint or log proof that fails verification
A package, an archive or a registry document fails verification. U7010 reports what failed and where it came from.
Why Una rejects it
A package of edition 0.4 is pinned by ita.lock to the content digest of each package it uses (ADR 0122, spec/30).
Every command that loads the package verifies, offline, each locked registry package it reads from the vendor directory or from Itaoca:
- Its files are read with no symbolic link followed, only regular files and directories, and only the paths a package may hold.
- The digest of the bytes read must be the lock's.
- The provenance stored beside it must verify against the lock: the source's root metadata from the pin in
ita.una, the checkpoint of the lock's resolution point with its log signature and its witnesses' cosignatures, and the release statement, its digest, its signature by the key the lock names, and its inclusion in that checkpoint.
una ita lock, update, add and fetch verify what they read from a registry the same way, from a mirror as from the source itself. A mirror that serves a copy that does not verify is skipped and named. This release has no https transport, so a registry is read only from a mirror directory that Itaoca's mirrors.una lists as a file:// URL. They verify:
- the root chain and its expiry,
- the checkpoint's witnesses, its freshness and its consistency with the one stored,
- every inclusion proof,
- each name's whole chain against the name map,
- the owner's keys at each statement's position,
- the archive against its statement, and
- that no release needs more authority or trust than the highest earlier one of its major line (rule 26).
U7010 reports what failed and where it came from:
- a vendored or stored package that was changed after it was fetched,
- a file a package may not hold,
- an archive that does not read,
- a provenance that does not verify,
- a registry or mirror whose files do not verify, or
- a mirror skipped for such a copy.
A vendored package that fails is not replaced by the copy in Itaoca.
una ita audit also reports evidence against a registry, at the source's registry section of ita.lock:
- An entry of an owner's chain that a registry following the rules never logs (spec/30 §14 rule 5, "What a registry logs"), naming the owner, its log index and the rule it was judged by. This also refuses the owner's packages.
- A release or a yank that its owner's keys as logged do not sign, which is skipped.
An owner's chain that is contested, where a claim of compromise that counts is void under the chain's compromises (spec/30 §14 rule 5, "Which claims count"), also refuses the owner's packages, while it stays contested. It is not evidence against the registry, and a later claim of compromise by the owner can resolve it.
How to fix it
There is no mechanical repair: a failure is evidence that the files were changed, or of an attack. Find out why, then remove the copy and vendor or fetch it again.
When una ita audit reports evidence against a registry, keep the registry's checkpoint and that chain's entries, and publish them. After such an entry the owner registers under a new owner name, with new keys, since a key that another owner's chain named is refused.
In the failing example, a file of the vendored release was edited after it was vendored. The fixed example shows the package once the dependency is no longer needed, since a self-contained example cannot carry a registry's signed files.
Failing example
ita demo
version 0.1.0
edition 0.4
sources
acme "https://ita.acme.example"
root "sha256:5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a"
needs
ledger 0.3 from acme-- Written by `una ita`; do not edit.
lock 1
solver
encoding "una-smt-1"
name "z3"
version "5.1.0"
logic "QF_UFLIA"
steps 5000000
seed 0
registry acme
root "sha256:5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a"
checkpoint 2 "sha256:0b7e3c110b7e3c110b7e3c110b7e3c110b7e3c110b7e3c110b7e3c110b7e3c11"
last root 1 "sha256:5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a5e0d1b7a"
package ledger 0.3.1
from acme
digest "sha256:3b1f8e0c3b1f8e0c3b1f8e0c3b1f8e0c3b1f8e0c3b1f8e0c3b1f8e0c3b1f8e0c"
signed "ed25519:itauna:7c0a91d27c0a91d27c0a91d27c0a91d27c0a91d27c0a91d27c0a91d27c0a91d2"
logged 1ita ledger
version 0.3.1
edition 0.4module ledger
pub total() -> Int = 4module demo
pub one() -> Int = 1Fixed example
ita demo
version 0.1.0
edition 0.4-- Written by `una ita`; do not edit.
lock 1
solver
encoding "una-smt-1"
name "z3"
version "5.1.0"
logic "QF_UFLIA"
steps 5000000
seed 0module demo
pub one() -> Int = 1