Fix Ghidra serializing negative 64-bit addresses#474
Merged
whyitfor merged 8 commits intoJun 7, 2024
Merged
Conversation
whyitfor
requested changes
Jun 5, 2024
Contributor
whyitfor
left a comment
There was a problem hiding this comment.
Please add a changelog to this MR
whyitfor
requested changes
Jun 6, 2024
Contributor
whyitfor
left a comment
There was a problem hiding this comment.
Looks good -- see a few minor comments/suggestions.
Contributor
|
LGTM. We should really use an actual JSON library in the ghidra scripts eventually. |
SamL98
approved these changes
Jun 7, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One sentence summary of this PR (This should go in the CHANGELOG!)
Link to Related Issue(s)
N/A
Please describe the changes in your request.
The OFRAK Ghidra scripts use
%dstring format of long integers when building JSON messages. In Java, this will be a signed decimal, but OFRAK expects an unsigned decimal. This causes problems in 64-bit Linux kernels, where commonly the address space is in the negative range. This change usesLong.toUnsignedStringto format all long integers as unsigned before serializing to JSON. This PR also adds a test case which uses an elf with a negative address range.Anyone you think should look at this, specifically?
@whyitfor @SamL98