Add an option to generate a file tree or index (per host) alongside downloaded loot, so an engagement produces a browsable directory listing in addition to the matched files themselves. This is useful for engagement reporting and gives context that is otherwise lost when only matching files are downloaded.
This feature was originally proposed in #23 by @glynx, who reported real benefit from the feature across multiple large engagements, including a text output and a JSON output intended for a future HTML viewer. That PR could not be merged directly because it predates significant refactoring across file.py, smb.py, spider.py, spiderling.py, and logger.py.
Add an option to generate a file tree or index (per host) alongside downloaded loot, so an engagement produces a browsable directory listing in addition to the matched files themselves. This is useful for engagement reporting and gives context that is otherwise lost when only matching files are downloaded.
This feature was originally proposed in #23 by @glynx, who reported real benefit from the feature across multiple large engagements, including a text output and a JSON output intended for a future HTML viewer. That PR could not be merged directly because it predates significant refactoring across
file.py,smb.py,spider.py,spiderling.py, andlogger.py.