-
Notifications
You must be signed in to change notification settings - Fork 61
tuftool: add manual testing steps for FIPS tuf repos #875
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
base: develop
Are you sure you want to change the base?
Conversation
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.
Nice work! Ran the tests and the runbook was super easy to follow.
57778fc
to
83e684b
Compare
83e684b
to
3a28ce4
Compare
^ force push uses local keys instead of relying on KMS |
6f49bfd
to
73180c8
Compare
^ force push runs containers in detached mode with steps to stop them by name, logs nginx errors to stdout |
Add instructions and resources for manually testing tuftool's FIPS feature to allow for easily repeatable testing. The instructions walk through creating a local TUF repo, serving the TUF repo via a Docker container, and downloading the repo via tuftool. Signed-off-by: Gavin Inglis <giinglis@amazon.com>
73180c8
to
a75bd17
Compare
^ force push writes access logs to stdout per @arnaldo2792 feedback |
Issue #, if available:
Related: #866
Description of changes:
Add instructions and resources for manually testing tuftool's FIPS feature to allow for easily repeatable testing. The instructions walk through creating a local TUF repo, serving the TUF repo via a Docker container, and downloading the repo via tuftool.
Testing:
Ran the testing instructions on a clean checkout of
tough
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.