From 562be3ff576a3e83ce564161245c100a18fee8c9 Mon Sep 17 00:00:00 2001 From: tv Date: Sun, 15 Nov 2026 20:23:27 +0000 Subject: continuum-signed: its reading of an envelope is best effort The reference client's check of an envelope takes some strings the server doesn't (padded base64, a meta field twice, a number written as a float). Only a string crafted so, from before a strict policy, gets there, and the server answers `409`; the comment says so. --- scripts/continuum-signed | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'scripts') diff --git a/scripts/continuum-signed b/scripts/continuum-signed index b4d9498..00d5c30 100755 --- a/scripts/continuum-signed +++ b/scripts/continuum-signed @@ -90,7 +90,9 @@ login() { # Whether $1 is an envelope as continuum reads one: `cv2.`, then the value, the meta and # the signature, each in base64url, the value one line of JSON and the meta one line -# holding its six fields, no more. Anything else is a plain value, replaced as one. +# holding its six fields, no more. Anything else is a plain value, replaced as one. Best +# effort: what the server reads decides, and a string crafted to read as one here and +# not there (padded, a field twice, a number written as a float) is answered `409`. is_envelope() { case $1 in cv2.*.*.*) ;; -- cgit v1.3.1