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
Crash when scanning text files containing a 0
byte in it
#155
Comments
0
byte in it
I recently bumped into this. Any news on a fix? |
Hi Jonathan, We don't have anyone working on this bug right now. I am going to propose it for our next sprint. |
@jhult I am looking into this, can you share more information about the file which caused the failure? What type was it? Was it corrupted? How long was it? |
Extract the decoding logic used when reading files from Docker images and reuse it when scanning files from the file system.
Extract the decoding logic used when reading files from Docker images and reuse it when scanning files from the file system.
Extract the decoding logic used when reading files from Docker images and reuse it when scanning files from the file system.
when will this be released into a version? |
We have a few issues to iron out in |
How's that release coming? We need this fix as well. |
Sorry for the delay, that one has been more complicated to wrap. We plan to release it next Monday. |
@rgajason ggshield 1.12.0 has just been released. |
GitGuardian Shield Version
Command executed
ggshield scan path ThirdPartyNotices.rtf
Describe the bug
ggshield crashes when scanning the attached file (attached as zip because GitHub does not support rtf files). This is because the final byte of the file is a 0, as can be seen on this hex dump:
Expected behavior
ggshield should either:
Traceback (if available)
The text was updated successfully, but these errors were encountered: