-
Notifications
You must be signed in to change notification settings - Fork 7
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
Sharing project files #3
Comments
I'm more in favour of making something that can be imported back into Ghidra/Ida, rather than putting the full project files on the repository (unless there's a good reason to do that). For labelling symbols, we can make a Ghidra/Ida script that renames the obfuscated names by using Do you think this could suffice? An alternative could be to have some sort of human readable form of the project (like Ghidra XML export) to ease versioning, but at that point i'd rather go with the source+scripts route. |
Yeah, I think that'd be cool. Something that could at least be imported back into those tools would actually be better than the project files. Not sure what I was thinking with that. I think it's possible to parse a C header into Ghidra, but I don't know how that works. I've never tried it myself |
656c217 adds a "slim header" that will be written to f84ef2c adds a CSV output in the form "name,section". An option that crossed my mind was to replace it with something that pulls the names from the compiled
However, this wouldn't work for the few symbols that lack a name. An alternative is to load the resulting In other words, it needs to be worked on further. |
Is it possible there could be a shared Ghidra/other RE tools project file(s) in the repo? This way as new information is found and more things are labeled, they can be labeled in other tools that make it easier to assess things.
The text was updated successfully, but these errors were encountered: