Repository navigation
Authorize the signer vectored I/O fix - #12
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Authorize signer c9cb62006a961a9fde1e653c96947fd57c602409: preserve partial readv/writev progress when a later buffer returns an error. The actual kernel syscall regression reproduced four bytes transferred followed by an incorrect EAGAIN return. That hidden progress can cause TLS callers to resend bytes. The source also adds typed HTTP status, timeout, and I/O-kind diagnostics without recording error messages, signed URLs, credentials, or paths.
The PCI-only image reproduced large-upload failures repeatedly. The new disposable-key candidate signed and uploaded both Google and OSS profiles of source run 38942735007 on the first attempt. Independent verification passed for receipts, unsigned provenance, payload preservation, Android signatures, code transparency, and rotation chains. MTU remains 9000. Final publication is still gated by the current central policy.
Advance test policy to revision 12 and prepared production policy to revision 5. Key fingerprints, workflow identities, and application constraints are unchanged. Production keys and Play publishing remain inactive.
Validation: 19 native tests; 3 actual vectored-I/O syscall regressions, including failure before/after progress and short transfers; PCI and timer regressions; QEMU TLS/webhook/audit smoke test; independently checked candidate signing. Image SHA-256: 0a302500262dc37b81c8dba6d4e9cf1c9f3ba2d99e6311badf6b319bc7fefdf1. The guarded build verified the actual kernel source directory. Full five-flow final attestation and publication verification follows approval.