-
Notifications
You must be signed in to change notification settings - Fork 8
Labels
Description
I think it'll be hard to do this programmatically, so we should just maintain a manual table of what we explicitly support, and why/how. Maybe a separate page on "supported targets". Table includes explicit loaders (e.g. VMX, SMB) but also containers (e.g. VMDK, E01), volume systems (e.g. LVM2, Linux RAID), filesystems (e.g. Btrfs, XFS), OS (e.g. FortiOS, ESXi) and child target plugins.
If it turns out we can easily automate this *nicely **, then that is preferred. But my gut feeling is that it'll look "cheap" and obviously auto generated. If we make it manual, we should add a CI test/Sphinx extension that throws a warning if there are more modules available in e.g. dissect.target.loaders.** then there are in the table.