-
v2.20.0
StableAll checks were successfulrelease / build-and-release (push) Successful in 24sreleased this
2026-11-07 15:04:44 +00:00 | 67 commits to main since this releaseNOE v2.20.0
This release corrects the contracts of existing Web Crypto operations, records
the remaining standard API gaps, and validates practical JWT/JWS use with an
unmodified SDK. Implementation checkpoints are6c8a23dand the deriveKey
error-order follow-up2e8a197. Runtime dependencies and the Go/v2module
path are unchanged.Corrected Web Crypto contracts
Supported operations remain SHA-1/256/384/512 digest, raw HMAC import/export /
sign/verify, and raw PBKDF2/HKDF import/deriveBits plus deriveKey to HMAC.- CryptoKey is a branded illegal constructor with readonly attributes and
cached visible metadata. Private snapshots govern material, algorithms,
usages and extractability. Mutating or shadowing metadata grants no authority. - Sign and verify require their own key usages independently. A verify-only
key cannot sign; verification does not additionally require sign permission.
Non-extractable HMAC keys cannot be exported through public-property changes. - Subtle methods copy BufferSource inputs with exact view offsets before
yielding. Ordinary arrays/strings, detached buffers and shared-backed inputs
reject with the specified errors. Registered Web names normalize ASCII case;
Node hash aliases do not extend the Web registry. - Import, derivation and export enforce key formats, usages, algorithm data,
length constraints and standard error names. Unsupported export operations
are checked before extractability. deriveKey checks base-key access before
executing target key-length validation, and needs no deriveBits permission. - HMAC's default derived length is the selected hash block size. The current
draft's zero-bit PBKDF2 result is supported after positive-iteration validation. - Native CPU calculations run off the VM owner when a Loop exists. Runtime /
Worker cleanup cancels and joins owned work, dropping undelivered results.
Legacy WebAPIs installation without a Loop may compute a settled promise. - getRandomValues enforces integer-view and 65,536-byte contracts with standard
DOMException names. Random-source selection and randomUUID v4 are preserved.
Behavior compatibility: callers relying on permissive key metadata,
cross-operation usages, non-BufferSource input coercion, Node hash aliases in
subtle, or previous error names must adapt. Import separate keys with the
required usages, request extractability at import when appropriate, and pass
ArrayBuffers or supported views. Node-style crypto helpers retain their own
byte/text conventions; their webcrypto/subtle exports remain identical to the
global objects. No new Profile field or host capability is required.Practical SDK proof and remaining gaps
The pinned, unmodified
jose6.2.15 Web API ESM distribution passes HS256 /
HS384/HS512 JWT/JWS signing and verification with raw and CryptoKey inputs,
modified-signature/expiration/issuer/audience rejection, main/Worker execution,
and two-way Node interoperability. SDK files retain their original fingerprints.
Node/npm prepare dependencies; NOE executes the fixture without patches or
polyfills. No real login or application-provider call is used.This does not claim complete Web Crypto or jose support. generateKey,
encrypt/decrypt, wrapKey/unwrapKey, native JWK/SPKI/PKCS8, public-key and
encryption algorithm families, full Crypto/SubtleCrypto interface shape, and
CryptoKey structured cloning remain unsupported. Cloning rejects DataCloneError;
Workers can import their own raw material. Actual SDK probes record generation,
CryptoKey JWK export, and AES-GCM JWE gaps.See the examples,
Go embedding guide,
API reference, and
contract, gap inventory and evidence.Verification and distribution
Implementation evidence covers affected units, focused race, declarations,
embedded docs, lint/vet, public Go consumers from checkout and source artifacts,
native cancellation, and actual SDK interoperability. A user-requested pi
review with GLM 5.3 / max completed; the parent verified its claims against
primary specifications and fixed the accepted error-precedence issue with a
baseline-failing regression. No independent fix re-review or full API audit
is claimed.Release verification reuses unchanged implementation evidence. CI builds the
six Linux/macOS/Windows amd64/arm64 binaries and SHA256SUMS from the immutable
tag without repeating source suites. Native execution is Linux amd64; other
targets receive build/checksum/metadata verification. Go 1.27.2, go-quickjs
v0.32.0, go-intl v0.8.0, CGO-disabled builds and disabled JIT remain selected.The release includes verified installation at both existing vm201 executable
paths with previous binaries retained. Other hosts, service restarts and
noebot changes are excluded. See the release checkpoints
for publication and installation evidence.Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
1 download
- CryptoKey is a branded illegal constructor with readonly attributes and