Repository navigation
Replace the pre-rename startset.exe CLI with a link to managedstatekeeper.exe - #31
Merged
Merged
Conversation
rodchristiansen
changed the title
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.
Fixes #30. The CLI was renamed from startset.exe to managedstatekeeper.exe, and because no current package owns startset.exe, upgrades left the old binary in place and on PATH, where it still ran unsigned payloads. Postinstall now replaces it with a symbolic link to managedstatekeeper.exe, so the old name keeps working and goes through signature enforcement. It uses a symbolic link because the MSI replaces managedstatekeeper.exe on upgrade, which would leave a hard link pointing at the old copy.