pouët.net

mikael information 6 glöps

• general:
• level: user
• personal:
• first name: Michał
• last name: Cudak

• 1k Windows FunPipes
• Quote:

  Sweet =) But why no music :D

  
  
  I know, I know... I will improve next time :)
• isokadded on the 2019-09-04 20:16:56
• demotool Windows Crinkler by Loonies [web] & TBC
• That's a very acceptable explanation. I have already learned some of the Crinklers specifics and I know that shorter code not always is a better compressed one...
• isokadded on the 2019-05-08 21:02:43
• demotool Windows Crinkler by Loonies [web] & TBC
• Quote:

  So you want a way to explicitly include a function in the import table even though nothing refers to it, and then somehow access the index at which it is placed, so you can use it in your code. Is this correct?

  
  
  Almost exactly ;) The true sentence is: even though nothing >>directly<< refers to it.
  
  I know the index in ImportTable as long, as the function is included. I just need to peek it up in Crinkler report and hardcode it back in my code.
  
  To be strict, instead of:
  
  
  Code: EXTERN _imp__ShowWindow@4:PROC ... call DWORD PTR [_imp_ShowWindow@4]; 2 + 4 bytes
  
  
  use:
  
  Code: EXTERN ImportTable lea EDI,ImportTable ... call DWORD PTR [EDI + offset to _imp_ShowWindow@4]; 2 + 1 bytes
  
  
  Right now the latter is only possible if the function was directly referenced before (but for a 1K majority of functions is called only once).
• isokadded on the 2019-05-08 13:38:58
• demotool Windows Crinkler by Loonies [web] & TBC
• Any chance for a switch which denies stripping unused code (/OPT:NOREF equivalent)?
  
  I'd like to mess with ImportTable by hardcoded offsets (it's a 3 byte call instead of 6 bytes), but this makes declared but indirectly called functions to be stripped away from ImportTable...
  
  Great work anyway.
• rulezadded on the 2019-04-30 17:07:08