docs: clarify checksum trust boundaries - #2162
Merged
cstamas merged 1 commit intoSep 26, 2026
Merged
Conversation
cstamas
approved these changes
Sep 26, 2026
|
@cstamas Please assign appropriate label to PR according to the type of change. |
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
2 participants
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
Clarify the distinction between transport-provided checksums, which verify integrity, and trusted checksums, which can detect changes to a local repository when independently protected.
Changes
Testing
git diff --check— passedmaster— only the two intended documentation files changed.No overlapping open pull request was found for #2042 or the checksum trust documentation. AI assistance was used to prepare this patch; the changes were reviewed for accuracy and scope.
Fixes #2042