-
Notifications
You must be signed in to change notification settings - Fork 32
Added evidence verify command for local verification #89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
4 tasks
87834a6 to
22444cf
Compare
selalererjfrog
approved these changes
Jun 24, 2025
dortam888
reviewed
Jun 25, 2025
08f921c to
24e7c26
Compare
alenon
requested changes
Jun 26, 2025
73e75b7 to
a9adb11
Compare
osaidwtd
reviewed
Jul 7, 2025
6b2e407 to
fd26adf
Compare
fd26adf to
a9ee2a2
Compare
527175b to
9ac174b
Compare
9ac174b to
85aa5a7
Compare
alenon
requested changes
Jul 10, 2025
Collaborator
alenon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dsse_test shold be removed
85aa5a7 to
584c3bd
Compare
alenon
approved these changes
Jul 10, 2025
584c3bd to
e2c0378
Compare
e2c0378 to
b144dc9
Compare
naveenku-jfrog
pushed a commit
to naveenku-jfrog/jfrog-cli-artifactory
that referenced
this pull request
Aug 13, 2025
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.
Evidence Verification Command for Artifacts, Packages, Release Bundles, and Builds
This command verifies evidences related to artifacts, packages, release bundles, and builds. It checks the SHA-256 hash of the subject against the SHA-256 hashes in each piece of evidence pinned to that subject, and verifies the signatures in each piece of evidence first with the provided keys and then with public keys in Artifactory. This functionality incorporates changes from this PR.
The command has the same arguments as the
jf evd createcommand for specifying the subject of verification:--build-name[Optional] Build name.--build-number[Optional] Build number.--package-name[Optional] Package name.--package-repo-name[Optional] Package repository name.--package-version[Optional] Package version.--project[Optional] Project key associated with the created evidence.--release-bundle[Optional] Release bundle name.--release-bundle-version[Optional] Release bundle version.--subject-repo-path[Optional] Full path to the subject's location.Additionally, three new arguments have been added. The first specifies the output type, and the second accepts public keys:
--format[Optional] Output format. Supported formats: 'json'.--keys[Optional] Paths to public keys for signature verification.--use-artifactory-keys[Default:false] When this option is set to true, the verify command fetches public keys from RT.Examples: