Repository navigation
fix(install): verify optional native providers only when installed - #238
Merged
Merged
Conversation
A fresh install of the default home profile never installs custody-provider (it belongs to the blockchain and full profiles), but installed-release admission required every native provider binary to exist. Home launch then refused with 'Installed release inputs require repair'. Verify a native provider when it is present or required by the home profile, as other components already are; a present provider still has to match its signed checksum.
andersalm
added a commit
that referenced
this pull request
Oct 5, 2026
…lizer alpha.3 is published with the fresh-install Home launch defect fixed in #238, so the fixed source ships as alpha.4 (install) and alpha.5 (update). The V4 finalizer only served the retired model-catalogue path.
15 of 18 tasks
andersalm
added a commit
that referenced
this pull request
Oct 6, 2026
…me journey (#89) The journey built old and new from the same commit, so no check updated a real older release to new code (alpha.6's provider refusal #245, alpha.3's fresh install #238). Old is now the newest published release, pinned by release CID and SHA-256 in scripts/update-hop-previous-release.json: its Runtime, Home support and source installer, fetched by signed hash and cached by the pin in CI. The fixture republishes them under its disposable key, so the hop proves the published code and data layout, not the maintainer key. Home installs old, updates through System to this build, then this build refuses a tampered later release. Data is written after the update; a plain update to old is refused; `elastos update --rollback-to <old head>` restores old; Home starts again with the same account, preference and data. Refusal seeds install new, so this source's update code refuses every case. check-result is the CI verdict on result.json. VERSIONING.md moves the pin after each publish.
andersalm
added a commit
that referenced
this pull request
Oct 6, 2026
…me journey (#89) The journey built old and new from the same commit, so no check updated a real older release to new code (alpha.6's provider refusal #245, alpha.3's fresh install #238). Old is now the newest published release, pinned by release CID and SHA-256 in scripts/update-hop-previous-release.json: its Runtime, Home support and source installer, fetched by signed hash and cached by the pin in CI. The fixture republishes them under its disposable key, so the hop proves the published code and data layout, not the maintainer key. Home installs old, updates through System to this build, then this build refuses a tampered later release. Data is written after the update; a plain update to old is refused; `elastos update --rollback-to <old head>` restores old; Home starts again with the same account, preference and data. Refusal seeds install new, so this source's update code refuses every case. check-result is the CI verdict on result.json. VERSIONING.md moves the pin after each publish.
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.
Part of #89. A fresh
install.shof 0.8.0-alpha.3 installs the defaulthomeprofile, which does not includecustody-provider. Installed-release admission (installed_release.rs, added in #230) required every native provider to exist, soelastos home --browserrefused with "Installed release inputs require repair". Found by the operator's fresh-install test of the published canary; installingcustody-providerby hand made Home start, create an account and show System "up to date".The fix verifies a native provider when it is present or required by the
homeprofile, the same rule other components already follow. A present provider still must match its signed checksum. The regression test covers optional absent (admitted), optional valid (admitted), optional changed (refused) and required absent (refused); it fails ondevelopat "optional absent".