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

Using Scalpel on Unallocated Space without dumping? #36

Open
passwordleak opened this issue May 10, 2019 · 1 comment
Open

Using Scalpel on Unallocated Space without dumping? #36

passwordleak opened this issue May 10, 2019 · 1 comment

Comments

@passwordleak
Copy link

I need to run scalpel on the unallocated space of a raw image. Based on everything I read online, this is done by first dumping the unallocated space to another file using blkls, and then running scalpel on that. However due to disk space constraints, this may not be possible. I don't see why scalpel can't theoretically run against the unallocated space on the raw image itself, without dumping. Is there anyway to do this currently?

@bcarrier
Copy link
Member

No. Scalpel doesn't know anything about file systems to know what is unallocated. We tried to do this with Autopsy and have it feed the unallocated space into scalpel in memory only, but scalpel had memory leaks and would eventually cause everything to stop working.

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

No branches or pull requests

2 participants