Skip to content
New issue

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

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

Already on GitHub? # to your account

Review disk image extraction workflows against workflows/scripts by Tim Walsh #4

Open
bitsgalore opened this issue Oct 19, 2018 · 0 comments

Comments

@bitsgalore
Copy link
Member

bitsgalore commented Oct 19, 2018

See:

https://www.bitarchivist.net/blog/2017-05-01-buf2017/

This seems to be better suited to our needs.

Question: not clear how script deals with disk images that have multiple partitions, as call to tsk_recover doesn' t use -o (offset) switch:

https://github.com/CCA-Public/diskimageprocessor/blob/master/diskimageprocessor.py#L436

Update: volumes with multiple partitions are not supported:

CCA-Public/diskimageprocessor#16

A possible refinement could be to parse the disktype output and iterate over all detected file systems.

Also tsk_recover doesn't keep original timestamps! Some ideas on this here:

https://twitter.com/dericed/status/968537979873648640

In particular (which is already implemented in Tim's script):

https://github.com/CCA-Public/diskimageprocessor/blob/master/diskimageprocessor.py#L446-L489

Note that Bitcurator's default workflow doesn't use tsk_recover but applies the icat tool on a file-by-file basis:

https://github.com/BitCurator/bitcurator-distro-tools/blob/master/bc_disk_access_v2.py#L1134

@bitsgalore bitsgalore changed the title Review current workflows against alternative workflows/scripts by Tim Walsh Review disk image extraction workflows against workflows/scripts by Tim Walsh Oct 19, 2018
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant