Harden software updates and prepare v1.0.1 release#30
Merged
Conversation
…-RMC/WPF-Framework into bug-fixes-and-enhancements
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.
Summary
Updater hardening
The installed updater previously ran in place, so an update containing new updater binaries could encounter Windows file locks. Archive extraction also wrote directly into the installation and could overwrite runtime-owned folders such as
settings.This change launches a complete updater payload from a GUID-named temp runner, preflights and stages archives before installation, permanently protects runtime-owned paths, and tracks overwritten and newly created files for rollback. Existing
UpdaterBootstrapper.LaunchUpdatercallers retain the original binary signature.Archive roots that already exist in the installation are never treated as removable release wrappers. This preserves application folders and ensures reparse-point checks run against their intended destination paths.
Validation