-
Notifications
You must be signed in to change notification settings - Fork 75
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
Ex01 Verify hash Failure #212
Comments
Which version of ewfverify did you run? Note that Ex01 support is experimental |
used build version 20240506 |
Can you provide the image or debug output to determine what might be different. Also see https://github.com/libyal/libewf/wiki/Troubleshooting#format-or-behavioral-errors |
compiler Visual Studio 2022 |
Thanks I have been able to reproduce will take a closer when time permits, as indicated previously note that version of libewf and Ex01 support is experimental |
I hope your experiment with libwf and Ex01 supported versions is successful |
Create Image
ewfacquire.exe -t case123_image -w -r 3 -g 128 -d sha1 -f encase7-v2 -C 123456 -M physical -e "John Doe" -E 001 -D "Disk evidence for case 123" -N "Acquired on 2023-12-12" -c deflate:best -r 3 -j 4 \.\PhysicalDrive1
Evidence segment file size in bytes (1.0 MiB <= value <= 7.9 EiB) [1.4 GiB]: 19 GiB
Default settings for remaining options
Which part of ewfVerify should I check?
ewfVerify.exe case123_image.Ex01
Ex01 file created with encase7-v2 option
ewfVerify results
MD5 hash stored in file: 72ef9b239d37c690bbbb2523883c55d8
MD5 hash calculated over data: 25543448a355affa5473d513176f6bd6
SHA1 hash stored in file: 1d50e793a1a3d9d4eff665666390482508d86a43
SHA1 hash calculated over data: b0009ba971971f8ff63ea7390004e4f038abf462
ewfVerify.exe case123_image.E01
E01 file generated by encase6 option
ewfVerify results
MD5 hash stored in file: 72ef9b239d37c690bbbb2523883c55d8
MD5 hash calculated over data: 72ef9b239d37c690bbbb2523883c55d8
SHA1 hash stored in file: 1d50e793a1a3d9d4eff665666390482508d86a43
SHA1 hash calculated over data: 1d50e793a1a3d9d4eff665666390482508d86a43
The text was updated successfully, but these errors were encountered: