Skip to content
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

Add CL_TYPE_PYTHON_COMPILED and associated file type magic signatures #1111

Merged
merged 2 commits into from
Dec 14, 2023

Conversation

micahsnyder
Copy link
Contributor

It may be necessary to differentiate between *.pyc and other binary types in case additional processing is needed.

Outside of being able to differentiate the by file type, the scanner will treat CL_TYPE_PYTHON_COMPILED the same as CL_TYPE_BINARY_DATA. That is - we're not adding parser at this time to further break down .pyc files.

It may be necessary to differentiate between *.pyc and other binary
types in case additional processing is needed.

Outside of being able to differentiate the by file type, the scanner
will treat CL_TYPE_PYTHON_COMPILED the same as CL_TYPE_BINARY_DATA.
That is - we're not adding parser at this time to further break down
.pyc files.
@micahsnyder micahsnyder requested a review from ragusaa December 13, 2023 03:31
@micahsnyder micahsnyder merged commit 1132209 into Cisco-Talos:main Dec 14, 2023
23 of 24 checks passed
@micahsnyder micahsnyder deleted the CLAM-1744-pyc-ftm branch December 14, 2023 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants