-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
r2 outputs incorrect ssdeep hashes for binary sections #23930
Comments
Note: this probably feels like a good first issue (though maybe I'm wrong)? Is there documentation to guide someone through their first PR and making sure tests/builds pass? I know this gets covered at r2con but it might be useful to exist in long-form writing if it doesn't already. |
See the DEVELOPERS.md |
I split the |
thanks for taking care of it :) |
No problem. I'm pretty sure I've tracked down the cause of the |
cool! looking forward your next pr |
Okay - this bug should be fixed in PR #23941. [0x100003a90]> iS ssdeep
nth paddr size vaddr vsize perm flags ssdeep type name
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
0 0x00003830 0x3c10 0x100003830 0x3c10 -r-x 0x0 24:xecd/8FGEE8Z6J/QJl38o38x8bzLbLyJgLVlnLeJLrrXLPLIgjjhob6qXK:xFE/w/QJbdLHyJOVtet/bTIgnmOy REGULAR 0.__TEXT.__text
1 0x00007440 0x520 0x100007440 0x520 -r-x 0x0 1:lllllllllllllllllllllllllllllllllllllllllllllllllllllllllllllll: SYMBOL_STUBS 1.__TEXT.__auth_stubs
2 0x00007960 0xdc 0x100007960 0xdc -r-x 0x0 3:Rbis8AaroSr4o4eANUFRtlU/sGYao05teAC/mef7HZlNCvlBAevsn:Wx1piU40S5teAg77NCvlBC REGULAR 2.__TEXT.__const
3 0x00007a3c 0x4e9 0x100007a3c 0x4e9 -r-x 0x0 24:HfvlIEf751ylc4cBcLo6d6sV36oYEhsQNGfltM0LtIsBNSntfTioY:Hf97fl1ohcBcLB3MQN2ysPibBY CSTRINGS 3.__TEXT.__cstring
4 0x00007f28 0xd8 0x100007f28 0xd8 -r-x 0x0 6:wUyeplqMyLtCLM+oMCgMligBpbwof/PUQ:Qwlf5kiE6of5 REGULAR 4.__TEXT.__unwind_info
5 0x00008000 0x290 0x100008000 0x290 -rw- 0x0 12:N+OK+tQR0i5B96/PZPr6cld+UBlBF2FKp7lVsV4JlziVNNnpMGfRB3fn:N+8tKd5B0/JPBlBF2FKp7cNNaABv NONLAZY_POINTERS 5.__DATA_CONST.__auth_got
6 0x00008290 0x30 0x100008290 0x30 -rw- 0x0 1:qh2kllmdnR3toYDSllNMXlltglQ7toY4dllN9XlltglqhNkln:qh2kURdouievWQGVnX9qlqAln NONLAZY_POINTERS 6.__DATA_CONST.__got
7 0x000082c0 0x268 0x1000082c0 0x268 -rw- 0x0 12:YZUFJj6p4T/tuP7+ltE/fg8SaRtHU4jLnmtd5FrblVUJC+ElwtSI1g0PRt1gGE:YZuJj6p4rmeu3gxaRm4jbEdYcKSIbptM REGULAR 7.__DATA_CONST.__const
8 0x0000c000 0x20 0x10000c000 0x20 -rw- 0x0 1:llllllllllllllllllllllllllllllll: REGULAR 8.__DATA.__data
9 0x00000000 0x0 0x10000c020 0xb0 -rw- 0x0 ZEROFILL 9.__DATA.__common
10 0x00000000 0x0 0x10000c0d0 0x150 -rw- 0x0 ZEROFILL 10.__DATA.__bss |
Environment
Description
When I try to view ssdeep hashes for a target binary's sections, the hash structure in the output is not a valid ssdeep hash. I would expect to see a valid ssdeep hash of the structure
block size : single chunk hash : double chunk hash
.Test
Using an example C "Hello, World" target:
The hash values remain the same if I try to output in JSON via
iSj
. The values also remain the same if I try to userabin2
via:One oddity to note in
rahash2
(for the full file hash) is that the output only seems incorrect in JSON.The text was updated successfully, but these errors were encountered: