Home / Docs / Diagnostics
U7014: A locked release yanked, under an advisory or signed after a stated compromise, or a pending recovery, a key change or a transfer of its owner
una ita audit finds a locked release that is yanked, named by an advisory or signed by a key later revoked as compromised, or a pending recovery or a key change of its owner. una ita lock and una ita update report a key change of an owner too.
Why Una rejects it
una ita audit checks the registry packages of ita.lock against each name's state at a fresh checkpoint of its registry, verified as every registry document is (ADR 0122 rule 41, spec/30 §15). 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. U7014 reports, once per package with every finding:
- a locked release that its owner has yanked;
- one that an advisory names;
- one signed by a key that was later revoked as compromised since a log entry before it; and,
- since the lock's resolution point, a recovery pending for its owner or a change of its owner's keys.
A lock keeps a yanked release, and una build stays offline and never calls the audit, so a project's release gate runs una ita audit and fails on U7014. una check does not report U7014.
The examples below are audited against a registry acme whose state has acme/ledger 0.3.1 yanked and 0.3.2 released, neither advised.
A package of edition 0.4 locks each registry release with the key that signed it (ADR 0122 rules 25 and 38, spec/30 §14). The keys of a package's owner are the ones its chain in the registry's log gives at each log position: keys added and revoked, a threshold, and recoveries and changes of recovery co-signers, which take effect only seven days of witness time after they were logged, unless a current key cancels them.
una ita lock and una ita update compare the owner's keys with the ones the lock was written under. Another signing key, or a key event of the owner logged after the lock's resolution point, a recovery or a co-signer change that took effect included, is a key change, and one still pending is reported too. U7014 reports it at the need, and nothing is written, so a stolen or recovered owner account never changes what a program runs without the programmer's consent.
A release signed after its key's stated compromise is skipped by new resolutions as a yanked one is.
How to fix it
- For a finding of
una ita audit, the repair is to raise the package withuna ita update <name>, which takes the next release that is neither yanked nor advised, or to find out why the owner's keys changed before taking anything new. - For a key change that
una ita lockoruna ita updatereports, the repair is to review the owner's key events in the registry's log, then to record the change withuna ita lock --accept-key <package>oruna ita update --accept-key <package>.
The repair at a glance
lock 1
solver
encoding "una-smt-1"
name "z3"
version "5.1.0"
logic "QF_UFLIA"
steps 5000000
seed 0
registry acme
root "sha256:5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e"
checkpoint 10 "sha256:d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4"
last root 1 "sha256:5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e"
- package acme/ledger 0.3.1
+ package acme/ledger 0.3.2
from acme
digest "sha256:3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b"Failing example
ita demo
version 0.1.0
edition 0.4
sources
acme "https://ita.acme.example"
root "sha256:5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e"
owners acme
needs
acme/ledger 0.3 from acmelock 1
solver
encoding "una-smt-1"
name "z3"
version "5.1.0"
logic "QF_UFLIA"
steps 5000000
seed 0
registry acme
root "sha256:5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e"
checkpoint 10 "sha256:d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4"
last root 1 "sha256:5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e"
package acme/ledger 0.3.1
from acme
digest "sha256:3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b"module demo
pub one() -> Int = 1Fixed example
ita demo
version 0.1.0
edition 0.4
sources
acme "https://ita.acme.example"
root "sha256:5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e"
owners acme
needs
acme/ledger 0.3 from acmelock 1
solver
encoding "una-smt-1"
name "z3"
version "5.1.0"
logic "QF_UFLIA"
steps 5000000
seed 0
registry acme
root "sha256:5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e"
checkpoint 10 "sha256:d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4d4"
last root 1 "sha256:5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e5e"
package acme/ledger 0.3.2
from acme
digest "sha256:3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b3b"module demo
pub one() -> Int = 1