Recover automatically from a protected suite-cache folder (1.3.0-rc.4) - #19
Merged
Merged
Conversation
An extraction folder left by an elevated or foreign-account run stays unreadable and undeletable for the normal user, so rc.3 only failed faster with instructions to delete it using administrator rights. Now the verified bytes go one step further: after the full archive, manifest, notice and clip verification passes, the client atomically installs the extraction into a deterministic writable location beside the blocked ".suite-pack" subtree, announces the recovery in the preparation event stream (GUI event log and CLI), and reuses that copy byte-for-byte on later starts. Nothing protected is deleted, taken over or trusted; when even the alternate location cannot be written the error names the actual permission cause and both paths. Freeze 1.3.0-rc.4 / client/0.3.3; protocol 7.1, admission minimum, suite bytes, frozen fingerprints and scientific settings unchanged.
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.
What changes
Release metadata
Freeze `1.3.0-rc.4` / `client/0.3.3`; run-page model retargeted (Windows digest stays null/honest-pending until the stamped follow-up); superseded section documents the published rc.3 pair with its digests; changelog entry added. Protocol 7.1, admission minimum, suite bytes, frozen fingerprints, scientific settings and backend untouched.