Skip to content
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

[New Plugin]: PSVitaLoader #283

Open
1 task done
computerman00 opened this issue Sep 19, 2024 · 1 comment
Open
1 task done

[New Plugin]: PSVitaLoader #283

computerman00 opened this issue Sep 19, 2024 · 1 comment
Labels
new plugin Adding a new plugin

Comments

@computerman00
Copy link

Plugin Description

A Binary Ninja Plugin for PRX2 PS Vita eboot.bin ELFs.

Dynamic linking of modules on the PS Vita is performed by NID(Numeric Identifier) of a function or variable instead of names. The primary purpose of this plugin is to resolve all import/export function/variable names, create symbols for them, and load them back into the default ELF BinaryView at their respective position. This plugin will also add PS Vita(PRX2) specific datatypes with locations in the binary resolved(if applicable). Additionally, this plugin attempts to do some cleanup resulting from the decompilation of the mixed ARMv7/thumb2 instruction sets, removing some misaligned/junk instructions in places where there should have been in-line data.

Included is a combined NID database from vitasdk used for the function and variable name resolution/lookup. A optional header file is included as well, also combined from vitasdk's vita-headers, if supplied all datatypes will be imported along with the sce* functions proper return type, argument names, and argument types.

Plugin Repository URL

Repo URL: https://github.com/computerman00/BinaryNinja-PSVitaLoader

Real Release

  • I have made a real release
@computerman00 computerman00 added the new plugin Adding a new plugin label Sep 19, 2024
@computerman00
Copy link
Author

I'm not sure if the above issue is automatically parsed so adding in a comment.

I went through a few of the plugin submission issues and noted that not including the longdescription field will result in the README getting pulled instead. Doing this, the generate_plugininfo.py -v plugin.json check fails but I did check out a few releases and noticed that they had skipped the field - let me know if this is an issue and I will resolve it as soon as I can.

On the same note, my README might be a bit too verbose, if you think that is the case I will add a shorter longdescription. I do hope to add a wiki that I can move(and expand) the examples into.

Please do let me know if you have any feedback or find any issues in the submission. Thanks for your time!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new plugin Adding a new plugin
Projects
None yet
Development

No branches or pull requests

1 participant