8000 Add Patch Management System for micropatches support · Issue #12 · VitorVilela7/UberASMTool · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Add Patch Management System for micropatches support #12

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.

Sign up for GitHub

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

Jump to bottom
Open
VitorVilela7 opened this issue May 16, 2019 · 2 comments
Open

Add Patch Management System for micropatches support #12

VitorVilela7 opened this issue May 16, 2019 · 2 comments
Labels
enhancement

Comments

@VitorVilela7
Copy link
Owner

All .asm patches are done by Asar but with absolutely no management system, no handlers for making sure the data is left intact, no hijack collision system and no patch uninstall system.

At least one that is reliable.

Add support for micropatches and patch management system for UberASM Tool.

Micropatches specifications:

  • Single freespace block
  • Delegate hijack control for UberASM Tool.
  • Removal support
  • Hijack sharing with UberASM.

Extra:

  • Remove hijacking support on normal UberASM Tool .asm files for extra security.
  • Have a online repository similar to nodejs.
@randomdude999
Copy link

"no hijack collision system" - do you mean checking that things that you're hijacking are what you expect? that's doable with just asar too, using if and read1. Admittedly it's a bit ugly, but could be put into a shared library.
"no patch uninstall system" - the unpatcher tool from smwc
"no management system" - i guess i can agree with this one a bit, but is a management system really that needed? you can just keep a directory with all your patches and only reapply them when you actually edit the patches.
"no handlers for making sure the data is left intact" - what do you mean by this?
"Have a online repository similar to nodejs." - isn't smwc's patches section good enough? ...though i guess that doesn't really have a specification for which file in the zip is the main one, but quite a lot of patches require configuration before they can be used anyways.

@VitorVilela7
Copy link
Owner Author

  1. Correct. There should be a better alternative for asar other than read1 and if in my opinion. Reading 4-16 bytes of block and comparing them immediately with a byte sequence or opcode sequence for data validation (including somehow check common changes like SA-1 RAM remap).

  2. Is it better than the previous attempts?

  3. It's always good for giving some improvement on that.

  4. basically data integrity. It's not very uncommon to part of the data get modified by another tool and end up being a crash source. LM already does it partially with its internal structures, but ASM patches usually are the ones that will likely trigger a crash on the ROM.

  5. Maybe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@randomdude999 @VitorVilela7
0