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

Problems reading images with encrypted/corrupt partitions #530

Closed
ghost opened this issue Sep 28, 2015 · 2 comments
Closed

Problems reading images with encrypted/corrupt partitions #530

ghost opened this issue Sep 28, 2015 · 2 comments

Comments

@ghost
Copy link

ghost commented Sep 28, 2015

Hello,

i have two different E01 images from two different cases. Both have several partitions with at least one encrypted partition and some unencrypted partitions.

Using AddImageProcess, I want to add those Images to the local .sqlite database. For the unencrypted partitions this works as expected, but as soon as TSK tries to read the encrypted partitions into the database a TskDataException is thrown and the process is stopped. What can I do to "bypass" reading the encrypted partitions, reading only the partitions into the database which TSK is able to read? Now I'm having the problem that as soon as the AddImageProcess is stopped, all the other data which can be read by TSK is also dropped.

@bcarrier
Copy link
Member

Are you sure it is stopping? We have several disk images where there is one or more partitions w/out file systems in them. If no file systems are ever found in the disk image, then nothing will be found. If a single file is found, then it will be added. The database is committed only if it successfully ends.

Is any data at all added to the database or not?

@ghost
Copy link
Author

ghost commented Oct 6, 2015

It starts adding data to the database, stops at around ~57MB database file size (I guess this is the point where it tries to read data from the encrypted/corrupt partition) for several seconds and then throws the TskDataException which results in a revert of all changes made to the database file (the database file size afterwards is 1MB).

If im reading it with tsk_loaddb command, it works just fine.

In case it is helpful, here is the output of "mmls" of the image file:

DOS Partition Table
Offset Sector: 0
Units are in 512-byte sectors

  Slot      Start        End          Length       Description

000: Meta 0000000000 0000000000 0000000001 Primary Table (#0)
001: ------- 0000000000 0000000062 0000000063 Unallocated
002: 000:000 0000000063 0020466809 0020466747 Unknown Type (0x27)
003: ------- 0020466810 0020467711 0000000902 Unallocated
004: 000:001 0020467712 0166793215 0146325504 DOS FAT16 (0x06)
005: 000:002 0166793216 0312578047 0145784832 NTFS / exFAT (0x07)
006: Meta 0312578048 1953521663 1640943616 Win95 Extended (0x0f)
007: Meta 0312578048 0312578048 0000000001 Extended Table (#1)
008: ------- 0312578048 0312580095 0000002048 Unallocated
009: 001:000 0312580096 1953521663 1640941568 NTFS / exFAT (0x07)

@ghost ghost closed this as completed Oct 28, 2015
This issue was closed.
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

1 participant