You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TL;DR: A secret saved in Python code, or text file, or pickle version 0 (which is pure ASCII) is found by tartufo. But all other pickle versions, where the content is binary but the secret string still clearly seen in file as is, are not picked up by tartufo.
Why I am writing this?
I discovered it in pure luck, for some RDAP unit tests I maintain, I store the expected output (which is a Python object linked to other Python objects, and I want to keep the details so I can't use JSON here in a trivial fashion) using pickle and I saw that the various high entropy strings (that were just public data here as RDAP is public but uses ROIDs which are opaque identifiers that can be considered high entropy) are not picked up by tartufo.
The text was updated successfully, but these errors were encountered:
It is just an observation, so neither a bug nor a feature request, but maybe it has merit to address.
In short: some given Python content that is stored encoded by the
pickle
module is not picked up for secrets, as the below shows.TL;DR: A secret saved in Python code, or text file, or pickle version 0 (which is pure ASCII) is found by tartufo. But all other pickle versions, where the content is binary but the secret string still clearly seen in file as is, are not picked up by tartufo.
Why I am writing this?
I discovered it in pure luck, for some RDAP unit tests I maintain, I store the expected output (which is a Python object linked to other Python objects, and I want to keep the details so I can't use JSON here in a trivial fashion) using
pickle
and I saw that the various high entropy strings (that were just public data here as RDAP is public but uses ROIDs which are opaque identifiers that can be considered high entropy) are not picked up by tartufo.The text was updated successfully, but these errors were encountered: