Skip to content

GHA: scan git repository and detect unvetted binary files - #14333

Closed
bagder wants to merge 2 commits into
masterfrom
bagder/GHA-binary-detector
Closed

bagder wants to merge 2 commits into
masterfrom
bagder/GHA-binary-detector

Conversation

@bagder

@bagder bagder commented Aug 1, 2024 •

Copy link
Copy Markdown
Member

The only binary-looking files that are accepted in the git repository need to match the sha256sum file .github/scripts/binarycheck.sums.

This is done to make sure that no one has planted any hidden (encrypted) potentially dangerous payload in the tree.

@bagder bagder added the CI Continuous Integration label Aug 1, 2024
The only binary-looking files that are accepted in the git repository
need to match the checksums in the sha256sum file
".github/scripts/binarycheck.sums".

This is done to make sure that no one has planted any hidden (encrypted)
potentially dangerous payload in the tree.

Closes #14333
@bagder
bagder force-pushed the bagder/GHA-binary-detector branch from b7fe158 to 83783fd Compare August 1, 2024 09:24
@bagder bagder closed this in e3240db Aug 1, 2024
@bagder
bagder deleted the bagder/GHA-binary-detector branch August 1, 2024 10:30
@dfandrich

dfandrich commented Aug 1, 2024 via email

Copy link
Copy Markdown
Contributor

@bagder

bagder commented Aug 1, 2024

Copy link
Copy Markdown
Member Author

Sure, but it's about raising reasonable "guard rails" here - not fooling anyone into saying that we can automatically detect any malicious payload. We don't accept large base encoded chunks either, but we reject those by manual review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Continuous Integration

Development

Successfully merging this pull request may close these issues.

2 participants