[SCITT] Re: A page for independent runs of the Vaara conformance vectors

e.dogru@conarium.dev Fri, 21 August 2026 11:45 UTC

Return-Path: <e.dogru@conarium.dev>
X-Original-To: scitt@mail2.ietf.org
Delivered-To: scitt@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id B7C1612D4DA98 for <scitt@mail2.ietf.org>; Fri, 21 Aug 2026 04:45:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1787312711; bh=flUDfIeW/+CEw1vrrfQ75gMQO5Z6jSmTwgaTPDOqH7I=; h=Cc:From:In-Reply-To:References:Subject:To:Date; b=JW1Tl7an3LMn+KHmcmoWUp/f9scz9ignDGKGKGUFaXW9An8FFfAOeBxdUTo9QyFUr 4c1qtNxW9JvoWex/zzV4BVdJhR43IPSjepTuI69Y8ATObezGe6NWg5BYR+EBLwPl59 7u7Sl/DD64OUUOzPiv3e6p4MZGkcjLRz4arrUT4U=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.618
X-Spam-Level:
X-Spam-Status: No, score=-1.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=conarium.dev
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PwXiGJLafiIW for <scitt@mail2.ietf.org>; Fri, 21 Aug 2026 04:45:11 -0700 (PDT)
Received: from bonobo.cedar.relay.mailchannels.net (bonobo.cedar.relay.mailchannels.net [23.83.210.22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 2AC9812D4DA95 for <scitt@ietf.org>; Fri, 21 Aug 2026 04:45:11 -0700 (PDT)
X-Sender-Id: hostingeremail|x-authuser|e.dogru@conarium.dev
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 921894E2FEF for <scitt@ietf.org>; Fri, 21 Aug 2026 11:45:04 +0000 (UTC)
Received: from fr-int-smtpout25.hostinger.io (trex-green-7.trex.outbound.svc.cluster.local [100.96.17.28]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 267744E3A54 for <scitt@ietf.org>; Fri, 21 Aug 2026 11:45:03 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authuser|e.dogru@conarium.dev
X-MC-Relay: Good
X-MailChannels-SenderId: hostingeremail|x-authuser|e.dogru@conarium.dev
X-MailChannels-Auth-Id: hostingeremail
X-Reign-Well-Made: 75c2b1486f22ebd2_1787312704500_2387509601
X-MC-Loop-Signature: 1787312704500:4276760279
X-MC-Ingress-Time: 1787312704500
Received: from fr-int-smtpout25.hostinger.io (fr-int-smtpout25.hostinger.io [148.222.54.38]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.96.17.28 (trex/8.0.2); Fri, 21 Aug 2026 11:45:04 +0000
Received: from localhost (34.86.89.34.bc.googleusercontent.com [IPv6:2a00:1d35:17a4:d900:51f5:85e2:e74c:e841]) (Authenticated sender: e.dogru@conarium.dev) by smtp.hostinger.com (smtp.hostinger.com) with ESMTPSA id 4hRJQ62hbdz1yMB for <scitt@ietf.org>; Fri, 21 Aug 2026 11:45:02 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=conarium.dev; s=hostingermail-a; t=1787312702; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=shdZQ+Pblp1F3cSCWysO6oDe4FCDfbY0547DMRBqZ1M=; b=BbcWiQ8WFn3uIPF98a+ikcS/lWSKksSFf4C2qVF4sKegfPVa8QouMrHWyxG4KjYMaM3sIY ph0xtUhjrwCTDhmmYSp2/ffuUGdrlIsiywcYg8Ika+yARivugGVyve/NmQd3R0QThZaCNt GlXpOz9Hrlxi5EuAcpGEirHsF8uTgSh1TrGqWBJlIfwJnRihQxl1GD9yCRQ5cvcFSjWYu7 g4dAfOofMEU3QWJUqyILmW2auDA0eFj1yeRlxV0Oj0pSYHfHiGrre5p3+a3n04TUfDivTH 06g87SB6rJ6WJk4aNtM3HKz6kFiGfNcXgg57757ts4zCDiQt1yhgXsDxbYJ0hg==
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"
From: e.dogru@conarium.dev
In-Reply-To: <CAOfgHgp1SQK6hAD49q6HgQKFf-oFTfzb7+TqeRqpXwCrWS28=Q@mail.gmail.com>
Message-Id: <1787312693967390114.1787312693@conarium.dev>
Mime-Version: 1.0
References: <TpUyxx5ABMjWSmfHKAapGrveJcPcen7ixrikIXT4TPILEwwp7bSORsZTKSCIack7ylQyz7tf_V4p4JiD6Ns0bnUoQ_pliWSJ_CsFLvStQEk=@vaara.io> <BYAPR19MB28069B0FEA3E8F8BB3474D28ADA42@BYAPR19MB2806.namprd19.prod.outlook.com> <Oy1hoH0AG0EmM4SI5S3sqz_u01myZ_S9OTioBGsSUr7AUH6P5FKrt1381rlyQsen-lZ3BoeM_vyodZ-OSpOARE6PSQsBkb8m1oflcrjDOts=@vaara.io> <CAOfgHgp1SQK6hAD49q6HgQKFf-oFTfzb7+TqeRqpXwCrWS28=Q@mail.gmail.com>
To: team=40emiliaprotocol.ai@dmarc.ietf.org
Date: Fri, 21 Aug 2026 11:45:02 +0000
X-CM-Envelope: MS4xfCJiKV5F/6F8QmSt65CP5sef3ij7jEbjG1oxnq250CV6cG64eb7u7lFfXvt0846Dr6DJ+irCMRLvYAE7ebq78z6FKPo00JWjh/uWfoTUbBYWKp+3DpK4 +LY1YTkw2NAuBemz7Atp1SDk0LYXbVEyRNC6ig7l8MyVqoNBVF4v7clnXYUm3zMZ9U8zP2omu0gvBSxC/hFH8+qOeIEpbhXv+4F5tjXtaFCYZF9ziySa3S+Q 7qRSlQTrT8jCRxQpWNi5xQ==
X-CM-Analysis: v=2.4 cv=V5Av0vni c=1 sm=1 tr=0 ts=6a883a3e a=RddCdUNZqxBAE8jYSUBS9Q==:617 a=1Q4z3441aVnbLEOd:21 a=xqWC_Br6kY4A:10 a=IkcTkHD0fZMA:10 a=48vgC7mUAAAA:8 a=x0tWzKjN2VyjcYcKG10A:9 a=j31DbLVt52nWk0M3:21 a=QEXdDO2ut3YA:10
X-AuthUser: e.dogru@conarium.dev
Message-ID-Hash: ZOOE6C5XFI7FU7GTHC7FSXX6TRXQUHVR
X-Message-ID-Hash: ZOOE6C5XFI7FU7GTHC7FSXX6TRXQUHVR
X-MailFrom: e.dogru@conarium.dev
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: scitt@ietf.org, hello@vaara.io, jhillier@certisyn.com
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [SCITT] Re: A page for independent runs of the Vaara conformance vectors
List-Id: "Supply Chain Integrity, Transparency, and Trust" <scitt.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/scitt/ZbDOktPT_m5Ijdqb9QDxa8h75x8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/scitt>
List-Help: <mailto:scitt-request@ietf.org?subject=help>
List-Owner: <mailto:scitt-owner@ietf.org>
List-Post: <mailto:scitt@ietf.org>
List-Subscribe: <mailto:scitt-join@ietf.org>
List-Unsubscribe: <mailto:scitt-leave@ietf.org>

Henri, Iman,

Iman — the publication-terms finding is the one I would fix before the rows start
arriving, and I can offer the language we ended up with rather than an opinion,
because we hit the identical wall and it took us two attempts.

A hash chain establishes that what you retained has not been rewritten. It says
nothing about what was removed from the end, because the remainder is a perfectly
valid shorter chain. Our verifier exits 0 on a chain whose last records were
deleted, and that is not a bug we have not got to — it is the only honest answer
available to a reader holding one file.

What we do instead is make the absence of the guarantee visible in the output,
rather than in a document nobody reads at verification time:

- an unpinned run prints a note on stderr and reports `"tailPinned": false` in
  its JSON, so a machine consuming the result cannot mistake *verified* for
  *verified to be complete*;
- a caller who retained an earlier head passes it back — `--expect-count` and
  `--expect-last-hash` — and a mismatch is the same exit code as a break in the
  middle, because a chain that is not the chain you pinned is not the chain you
  pinned;
- the head is separately anchored to an external log, which is the only thing
  that turns "detectable relative to a retained head" into "detectable at all".

So your second wording is the one I would take, and I would put it on the page
rather than only in the terms: *removal is detectable relative to a retained
head.* A reader who never retained one has been told something true and something
useless, and telling them which is the whole job.

Henri — a page that records a run disagreeing with yours, with the reason stated
and no blacklist, is the part that will be copied. It is the same property as a
negative vector: the disagreements are what earn the set.

Emek


On Fri, Aug 21, 2026 at 8:42 AM Iman Schrock <team=40emiliaprotocol.ai@dmarc.ietf.org> wrote:
Henri, Joel,

I ran the public corpus from a fresh checkout at commit
62a7080b7c854173c7d6b8ee51ce4dd724d59227 using Python 3.14.5. The
aggregate result was 41 suites passed, 0 failed, and 3 skipped across
44 suites. The new release_condition_v0 lane passed all eight cases.

That is a reproduction of the author-supplied checkers and vectors,
not an independent implementation or validation of the specification
text.

I did find one issue in the publication terms before filing a row. The
form says the maintainer cannot remove a row because the rows are
hash-chained. The chain makes rewriting detectable only to someone who
retained or independently witnessed an earlier head. If the same
operator controls the branch and the published page, the chain alone
cannot make deletion impossible.

I think the clean fix is either to publish each head through an
independent witness or anchor, or narrow the wording to say removal is
detectable relative to a retained head. With that correction, I would
be comfortable filing the run.

Best,
Iman

--
SCITT mailing list -- scitt@ietf.org
To unsubscribe send an email to scitt-leave@ietf.org