Repository navigation
fix(guest): safely write KMS key output - #890
Merged
Merged
Conversation
kvinwang
force-pushed
the
codex/fix-guest-kms-key-permissions
branch
from
August 4, 2026 08:48
7b03dde to
33099da
Compare
kvinwang
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
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
Protect the KMS key output with the repository's existing
safe-writedependency.Changes
safe_write_with_mode(..., 0o600).Verification
cargo check --manifest-path dstack/Cargo.toml -p dstack-utilcargo fmt --manifest-path dstack/Cargo.toml --allgit diff --check