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
Description
Now that RAW_TEXT events are being raised from parsed FILESYSTEM events (And corrections have been made to scope distance of such events/yara rules have been implemented) the next step should be to make changes to the internal excavate.py module to consume RAW_TEXT and extract useful tidbits (URLS/DNS_NAMES etc.)
As the data of RAW_TEXT events is a string instead of an object (as in HTTP_RESPONSE) the handle_event() of excavate might require changes.
This is a super exciting feature. Feeding the contents of binary files like PDFs and word docs into excavate is a pretty unique capability, that will only get more insane as we keep adding filetypes. I'm imagining being able to download an app from the app store, decompile it, and feed its entire contents into excavate and trufflehog 🙌
Description
Now that
RAW_TEXT
events are being raised from parsedFILESYSTEM
events (And corrections have been made to scope distance of such events/yara rules have been implemented) the next step should be to make changes to the internalexcavate.py
module to consumeRAW_TEXT
and extract useful tidbits (URLS/DNS_NAMES etc.)As the data of
RAW_TEXT
events is a string instead of an object (as inHTTP_RESPONSE
) thehandle_event()
of excavate might require changes.This is the error im getting currently
I have some time so will look into this this week
The text was updated successfully, but these errors were encountered: