-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Docker Image Identification in Tar Files #1643
base: main
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.
Overall looks great. Some small comments and just some Go style tweaks. Awesome job!!
🎉
@ahrav I moved the integration test into a separate file (and made the updates you suggested), but it's throwing an error. Locally it worked great. This is what I'm seeing:
|
Oh i wonder if the runner timed out after the 5 min interval. We can try to increase the timeout from 5m to test. |
@joeleonjr would this solve #674 ? |
Good catch. Yes, this closes #674 |
Description:
The scanner will currently untar a file and look through the archive for secrets; however, this approach misses secrets hidden in Docker image layers. (The
docker save
command turns docker images into tar files.) This PR adds docker image scanning inside all archived files identified as theapplication/x-tar
mimetype. A use-case for this feature would be scanning a filesystem, identifying tar files, and then checking if any of them are docker images.Checklist:
make test-community
)?make lint
this requires golangci-lint)?