Skip to content

v2.2.6 Public Evaluation — IETF 126 PermitReceipt Review Packet

Latest
Latest

Choose a tag to compare

View all tags
@meridianverity meridianverity released this 10 Jul 16:42
v2.2.6-public-eval
df89a84
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Important

Portable reviewer-path erratum — resolved

The frozen v2.2.6 guide disables build isolation before the declared build requirements are available in a fresh environment.

Use:

python -m pip install -r requirements.txt
python -m pip install -e . --no-deps

External same-environment retest on Windows 11 x86_64, CPython 3.12.10, and pip 25.0.1:

IETF review packet:               20 / 20 PASS
Independent recomputation:        17 / 17 PASS
Independent crypto verification:  19 / 19 PASS

No manual build-backend bootstrap was required. The certified CPython 3.13 / Linux x86_64 path and all frozen release assets remain unchanged. No PermitReceipt semantic, cryptographic-verification, or frozen-byte impact was observed.

Evidence: Issue #1

This release is the active canonical public-evaluation pointer for PermitReceipt / ORPRG coordination around the IETF 126 Hackathon and for reproducible running-code review.

The packet asks one narrow question:

Before a protected external effect commits, is there current, scope-bound permit evidence authorizing that exact effect?

v2.2.6 hardening

v2.2.6 supersedes v2.2.5 and closes the interoperability, fail-closed, replay, timestamp, revocation, capability-binding, ingress, reviewer-command, dependency-lock, and release-integrity issues identified during the v2.2.5 public evaluation.

Highlights include:

  • strict machine-schema parity for generated authorization-reference objects;
  • fail-closed handling across the recognized malformed-input paths exercised by the public packet;
  • mandatory typed anti-replay evidence and transactional replay reservations;
  • mandatory replay and capability verification before any constrained-mode ALLOW;
  • RFC 3339 parsing requiring an explicit time-zone offset, with absolute clock-drift enforcement;
  • strict revocation-status precedence and cryptographic capability-to-receipt binding;
  • duplicate-key, floating-point, integer-range, size, depth, and canonicalization boundary checks;
  • independent Ed25519 verification, including tamper-negative cases;
  • a hash-locked CPython 3.13 Linux QA environment, with runtime, test, and build-backend dependencies pinned;
  • deterministic ZIP_STORE packaging with a ZIP-specific SHA-256 sidecar, member-level manifest, and source-revision-bound provenance; and
  • end-to-end execution of the public toolchain through make qa-full.

Reproducible evaluation evidence

The frozen v2.2.6 release gate records:

Strict pytest:                     323 / 323 PASS
Evaluation vectors:                76 / 76 PASS
IETF selected review packet:       20 / 20 PASS
Independent recomputation:         17 / 17 PASS
Independent crypto verification:   19 / 19 PASS
Extended public runners:           21 / 21 PASS

orprg_eval statement coverage:      99.33%
orprg_eval branch coverage:         98.44%
Security-core line coverage:       100.00%
Security-core branch coverage:      99.705%
Verifier branch coverage:          100.00%
Strict-schema branch coverage:     100.00%

Canonical release assets

The canonical release tuple consists of:

  • the public-evaluation ZIP;
  • its ZIP-specific SHA-256 sidecar;
  • the member-level release manifest; and
  • the source-revision-bound provenance statement.

Reviewers should verify the release-asset digest before running or redistributing the packet.

Evaluation boundary

This release is a synthetic public-evaluation and interoperability-review artifact. It is not a production deployment, production security assurance, conformance certification, standards certification, or IETF endorsement.

The packet does not grant patent rights or production-use rights. Production deployment architecture, operational trust infrastructure, private conformance materials, commercial support, and applicable patent or licensing rights remain outside the public-evaluation boundary.

Assets 6
Loading