Repository navigation
break-glass: integrity check over plain HTTP; release record panel gap and strip - #82
Merged
Merged
Conversation
…d's break-glass panel gets its gap and strip - RecordingPlayer said 'integrity not checked' for every recording: crypto.subtle exists only in a secure context and this Backstage is served over plain HTTP. sha256Hex now falls back to a plain-JS SHA-256 (FIPS 180-4 vectors tested, including the padding boundary and a million bytes), so the SHA-256 check works everywhere. - ReleaseRecordDetail: the 'Break-glass sessions during this release' panel hugged the columns above and had no colour strip; now the same 18 px gap as Human context and a strip in the break-glass red. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
jfillman
force-pushed
the
breakglass-ui-fixes
branch
from
October 12, 2026 04:57
940655f to
c5d0176
Compare
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
1 participant
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.
Two things found in the browser on 2026-10-12.
crypto.subtleexists only in a secure context (HTTPS or localhost); this Backstage is served over plain HTTP, so the player could not hash.sha256Hexnow falls back to a plain-JS SHA-256 (tested against the FIPS 180-4 vectors, the 55/64-byte padding boundary and a million bytes, and against Node's digest). The SHA-256 matches the session record chip now appears everywhere.🤖 Generated with Claude Code