Skip to content

ci(stable): accept apksigner digest labels without weakening the fingerprint check - #18

Merged
Noirero merged 1 commit into
mainfrom
ci/stable-certificate-parser-20261113
Nov 13, 2026
Merged

Noirero merged 1 commit into
mainfrom
ci/stable-certificate-parser-20261113

Conversation

@Noirero

@Noirero Noirero commented Nov 13, 2026

Copy link
Copy Markdown
Owner

Run #43358461417 built all three APKs, then rejected a matching certificate because apksigner printed V2 Signer: instead of Signer #1.

Update the same parser in both Stable workflows. Keep apksigner verification and the pinned fingerprint. Require at least one valid 64-hex certificate SHA-256 digest and reject any different or malformed reported certificate digest. No changes to secrets, triggers, publication, or app source.

Local Bash fixtures passed: V2 label, legacy numbered label with uppercase digest, matching V2/V3, missing SHA-256, wrong digest, extra characters, and mixed digests. After CI/review and integration, freshly dispatch only Fiyora Stable Candidate (manual) from main; rerunning the old run would reuse its old SHA.

@Noirero
Noirero marked this pull request as ready for review November 13, 2026 06:34
@Noirero
Noirero merged commit eeb60e2 into main Nov 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant