-
Notifications
You must be signed in to change notification settings - Fork 168
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
Implement cryptographic validation of all payload and metadata in a zarf package #23
Labels
Comments
jeff-mccoy
added a commit
that referenced
this issue
Feb 8, 2022
Signed-off-by: Jeff McCoy <code@jeffm.us>
@Racer159 Are you actively working on this? If so could you please move it to doing now on the project board? I may get rid of it if we don't fine value in it long term, but I like the visual nature of it. |
#32 May be related / be a subtask of this. |
Dropped myself as an assignee, this is still a backlog task, I just added myself to not forget about it at the time |
Noxsios
pushed a commit
that referenced
this issue
Mar 8, 2023
Signed-off-by: Jeff McCoy <code@jeffm.us>
Racer159
added a commit
that referenced
this issue
Mar 31, 2023
Fixes: #23 --------- Signed-off-by: Jon Perry <yrrepnoj@gmail.com> Co-authored-by: razzle <harry@razzle.cloud> Co-authored-by: Wayne Starr <Racer159@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implement hashing/signing for all elements of the package to ensure authenticity and integrity of the artifacts.
Migrated from https://repo1.dso.mil/platform-one/big-bang/apps/product-tools/zarf/-/issues/36
The text was updated successfully, but these errors were encountered: