Harden update, credential, and release trust boundaries - #121
Draft
danielpiva wants to merge 1 commit into
Draft
Conversation
13 tasks
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
--local-model, disabled remote control-panel delivery/updates, and a strippedGITSTOREenvironment variable.123456API key with an OS-random 256-bit key, rotate legacy/example keys, retain at least one key, and write managed configuration files with owner-only permissions on Unix.event-listener,nanoid, andpostcss).Security notes
The core asset check now binds installation to GitHub's release metadata and exact official paths. This detects missing, corrupt, or mismatched assets, but it is still maintainer-controlled metadata rather than independent code signing.
Existing installations that still use the legacy
123456API key will rotate it on startup. Managed clients may need their configuration reapplied so they receive the new key.Validation
cargo fmt --manifest-path src-tauri/Cargo.toml -- --checkcargo test --manifest-path src-tauri/Cargo.toml— 201 passedcargo clippy --manifest-path src-tauri/Cargo.toml --all-targets -- -D warningsbun run checkbun test— 115 passedbun run buildbun audit --production— no vulnerabilitiescargo audit --file src-tauri/Cargo.lock— no vulnerabilities; 18 allowed transitive warnings remain (primarily Tauri's GTK3 stack, plus the existingglibiterator advisory)zizmor --strict-collection --offline .github— cleantauri build --no-bundle— optimized application built successfully on macOSThis is intentionally a draft because the update and credential changes alter security-sensitive behavior across all supported platforms.