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've encountered an issue where windows OS plugin wouldn't load when loading from tar.
Following my investigation I have found the issue is resulting of confusion between the loader and windows os plugin:
Hello @AlonHaviv1 thanks for bringing this issue to us.
I have looked into it, and think that changing the default to case_sensitive=False inside the tar loader wouldn't be the best solution as it would also impact those tar files that need to be case sensitive. E.g. information that was on a unix like filesystem.
The reason we use lower case for most windows systems, is because their filesystems are usually case insensitive.
I couldn't quickly identify another workaround within the dissect tooling, so this will be taken up when time allows.
You could however untar it, move everything under a fs/sysvol directory and tar it again. If you do that, the target-* tooling should pick it up.
If you have another suggestion or question please feel free to share.
I've encountered an issue where windows OS plugin wouldn't load when loading from tar.
Following my investigation I have found the issue is resulting of confusion between the loader and windows os plugin:
dissect.target/dissect/target/plugins/os/windows/_os.py
Lines 39 to 42 in aab863c
The windows here is lower case, contrasting the real folder name, which is
Windows
.In tar loader, when the tar is not from acquire the filesystem will load with
case_sensitive=True
flag:dissect.target/dissect/target/loaders/tar.py
Lines 53 to 59 in aab863c
Therefore, there is a contradiction between those.
I would love to open a PR to fix that, but I'm not sure if any change will break other loaders that rely on that condition.
The text was updated successfully, but these errors were encountered: