feat: add verity command for data integrity verification #57
+360
−0
Conversation
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
This commit introduces a new `verity` subcommand to support content integrity verification of data directories using cryptographic hashing (SHA-256). The `verity` command includes three subcommands: - `format`: Scans a data directory, computes SHA-256 hashes for all files, generates metadata (JSON), and outputs a root hash representing the entire directory state. - `verify`: Validates the integrity of a data directory against a known root hash and metadata file, ensuring no files have been modified. - `dump`: Extracts and displays either the full metadata or the root hash from an existing metadata file. Metadata is saved as a JSON file (`cryptpilot.metadata.json` by default), listing each file path and its corresponding hash. The root hash is derived from the serialized metadata, enabling secure anchoring in trusted environments. Implementation details: - New CLI structures added in `cli.rs` with proper argument parsing. - Modular command implementation under `src/cmd/verity/`. - Integration into the global command dispatch via `IntoCommand`. - Files are processed asynchronously using `tokio` and `async_walkdir`. - Excludes metadata file during scanning to prevent self-inclusion. This feature is useful for verifying system-critical directories during boot or in security-sensitive workflows. Signed-off-by: Kun Lai <laikun@linux.alibaba.com>
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.
This commit introduces a new
veritysubcommand to support content integrity verification of data directories using cryptographic hashing (SHA-256).The
veritycommand includes three subcommands:format: Scans a data directory, computes SHA-256 hashes for all files, generates metadata (JSON), and outputs a root hash representing the entire directory state.verify: Validates the integrity of a data directory against a known root hash and metadata file, ensuring no files have been modified.dump: Extracts and displays either the full metadata or the root hash from an existing metadata file.Metadata is saved as a JSON file (
cryptpilot.metadata.jsonby default), listing each file path and its corresponding hash. The root hash is derived from the serialized metadata, enabling secure anchoring in trusted environments.Implementation details:
cli.rswith proper argument parsing.src/cmd/verity/.IntoCommand.tokioandasync_walkdir.This feature is useful for verifying system-critical directories during boot or in security-sensitive workflows.