U++ framework
Do not panic. Ask here before giving up.

Home » Developing U++ » U++ Developers corner » Considering different approach to Win32 release
Re: Considering different approach to Win32 release [message #45385 is a reply to message #45376] Tue, 03 November 2015 09:52 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 14291
Registered: November 2005
Ultimate Member
mdelfede wrote on Mon, 02 November 2015 18:10

Or, better said, a possible solution would be to leave fixups unencrypted, but then we'd need a table somewhere to tell decrypter to leave them alone. Not an easy task either, and would entail the complete PE header analysis.


Maybe you could limit crypting only to specific opcodes... I believe that only "absolute address" opcodes are 'dangerous'.

You could use ndisasm for testing (although it is a bit disgusting to use opensource to close the source Smile

Mirek
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message icon14.gif
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: mingw/gdb troubles
Next Topic: Ideas on U++ as library
Goto Forum:
  


Current Time: Thu Sep 17 03:22:09 GMT+2 2026

Total time taken to generate the page: 0.01733 seconds