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
I think we should consider formalizing a file format for manticore workspaces.
Currently data is spread across many folders as each run creates a workspace folder and respective workspace files. This proposal would be to consolidate runs and individual files into a single workspace file/db that is exposed via API alongside a companion CLI for reviewing logs / exporting data on the command line. I saw there is or was support for redis? but this adds a requirement of running a redis instance which is undesirable.
The idea is to consolidate output from multiple sessions into a single file, add APIs for interacting with workspace data while not limiting or hindering the ability to filter or pipe that data to others tools from the CLI.
This should be discussed more in depth but my thoughts are something along the lines of a CLI (backed by an API) util that acts as a swiss army knife for extracting session information and managing session data across all possible sessions. I think this could potentially benefit integration efforts of other projects that will be consuming manticore output.
@feliam mentioned interest in using the shelve module.
The text was updated successfully, but these errors were encountered:
What's a "session" there ?
Current workspace folder thing lacks a .ini file that allow to reproduce/pause/restart the same exploration.
Related to . #372
I think we should consider formalizing a file format for manticore workspaces.
Currently data is spread across many folders as each run creates a workspace folder and respective workspace files. This proposal would be to consolidate runs and individual files into a single workspace file/db that is exposed via API alongside a companion CLI for reviewing logs / exporting data on the command line. I saw there is or was support for redis? but this adds a requirement of running a redis instance which is undesirable.
The idea is to consolidate output from multiple sessions into a single file, add APIs for interacting with workspace data while not limiting or hindering the ability to filter or pipe that data to others tools from the CLI.
This should be discussed more in depth but my thoughts are something along the lines of a CLI (backed by an API) util that acts as a swiss army knife for extracting session information and managing session data across all possible sessions. I think this could potentially benefit integration efforts of other projects that will be consuming manticore output.
@feliam mentioned interest in using the shelve module.
The text was updated successfully, but these errors were encountered: