Conversation
Shows the current version right-aligned at the bottom of the window, matching giu's own Align(AlignRight) math applied by hand (Align has a documented bug that skips Selectable, so it can't be used directly for a clickable label). Clicking it checks the latest GitHub release. If newer, a modal shows the release notes and an "Update Now" button - nothing is downloaded or applied without that explicit click. Update flow: 1. Download the new exe to a temp file 2. Verify its SHA-256 against the checksum published in the release notes; abort if it doesn't match 3. Rename the running exe aside (Windows allows renaming an exe out from under itself, unlike overwriting it), move the verified exe into place, spawn it as a new process, then exit 4. Any leftover .old file from a previous update is cleaned up on the next launch No automatic/background checking - matches Picocrypt's original "zero network requests" stance except when the user explicitly clicks to check, which is now documented in the README's Security section.
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.
Adds a version label at the bottom-right of the window. Clicking it checks the latest GitHub release; if newer, shows release notes in a modal with an explicit "Update Now" button. Nothing downloads or applies automatically - matches the discussion on issue-adjacent design questions (manual check, confirmed apply).
Update mechanism: download to temp -> verify SHA-256 against the checksum published in the release notes (aborts if mismatched) -> rename the running exe aside -> move the verified exe into place -> spawn it -> exit. Works the same for portable-exe and MSI-installed setups since both just put ZeeCrypt.exe in a normal per-user-writable folder.
Caveats, please read before merging/testing: