[sean0407]

Issue

Fixes #236. Test cases 367 and 370 carried the same compact JWS as valid test case 357, so their invalidBase64Padding labels did not match the encoded input.

Change

• Add forbidden Base64 padding to the signature segment in test case 367.
• Add forbidden Base64 padding to the payload segment in test case 370 and recompute its HMAC-SHA256 signature over the padded payload.

Verification

• GOEXPERIMENT=jsonv2 go run ./tools/vectorgen fmt --check 'testvectors_v1/*.json' — passed.
• GOEXPERIMENT=jsonv2 go run ./tools/vectorgen lint — passed: 343 valid vector files, 0 invalid, 0 without a schema.
• Independent HMAC-SHA256 checks confirmed the corrected signature bytes match the respective JWS signing inputs.
• git diff --check — passed.

[cpu]

Vector Lint / gostaticcheck (pull_request) Failing after 1m

Would you mind rebasing on current main? This should fix itself afterwards.

[sean0407]

I rebased the commit onto current main; the stable patch-id is unchanged and git diff --check passes. The latest run has vectorlint, gostaticcheck, and golint green; govulncheck fails on GO-2026-6809 in the Go standard library (crypto/x509 in Go 1.27.2), reached from tools/vectorgen/main.go. Could you confirm whether that repository-level toolchain finding should stay outside this test-vector change?

[botovq]

Another rebase onto main will pick up #283 and should fix the failing test.

[sean0407]

Rebased codex/fix-jws-padding-vectors-236 onto current upstream main, including merged #283 (d17cc89). The patch-id remains unchanged (95e99ff), and git diff --check passed. GitHub has started a fresh run; govulncheck and the other checks are currently pending.

[sean0407]

Update: GitHub’s fresh checks on rebased head 7db7db3 have all passed: golint, gostaticcheck, govulncheck, and vectorlint.

[sean0407]

I rebased onto current main with #283; govulncheck, gostaticcheck, golint, and vectorlint all pass on 7db7db3. Please let me know if anything else is needed, or merge when convenient.