Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Target shell fails to detect new files in EXT4 filesystems #695

Open
Paradoxis opened this issue Apr 30, 2024 · 0 comments · May be fixed by #694
Open

Target shell fails to detect new files in EXT4 filesystems #695

Paradoxis opened this issue Apr 30, 2024 · 0 comments · May be fixed by #694

Comments

@Paradoxis
Copy link
Contributor

Whenever I'm using target-shell against a live system, and the filesystem is updated, target-shell becomes out of sync with the actual file on disk. This primarily happens to me whenever a linux-based system is dissected, which in my case was a VMWare VM with a Linux guest on it with an EXT4 filesystem. For example:

image

In this example I'm running taget-shell on a virtual machine, with the CLI open before the file is dropped on the left, and a new instance of target-shell open after I drop the file and flush all open buffers on the right. I believe the shell fails to detect a filesystem change in the left most filesystem, and hence uses an outdated cache.

Note that this does not seem to be the case for windows guests though (caveat that this requires some waiting for the files to be flushed by the Windows OS):

image

A solution to this could be something like a sync command for taget-shell as I've tried to create in #694 (word of warning: might need some more testing), or it might be a bug in the EXT4 filesystem itself.

Thank you for listening to my TED talk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant