-
Notifications
You must be signed in to change notification settings - Fork 10
Description
I don't know if there is a use case for the raw extractor as it is right now. But for me it doesn't make much sense in extracting a file and name it after its hash code when the actual filename is listed in the directory entries or can be guessed. On the other hand, when extracting an archive using filenames, I want to know what is left over so I can have a look into (only) these cases.
So my suggestion is to remove HashFsRawExtractor. Change the --raw option to be an additional option instead of a main functional switch. When using HashFsExtractor and its Deep variant keep track of the hash codes that could be extracted by filename and at the end, if --raw is given, extract all remaining file entries into a separate directory named e.g. _unknown or _raw.
What do you think about this?