here is a way how powerbasic solves this problem for inspiration to the blitz-team:
Macro SECUREBEGIN = !DB &hEB,&h03,&hD6,&hD6,&h00
Macro SECUREEND = !DB &hEB,&h03,&hD6,&hD6,&hFF
Macros are not really required, its just an example.
Well, it would be nice to insert Opcodes and its an important feature to enable known good protection-systems like Armadillo, Asprotect and the upcoming protections-system from oreans (Themidia or so).
I think all good protectors are needing markers to encrypt data of the code or to NOP it out if a license is missing, so using this technology would be nice. It is available in all known programming-languages. Delphi, C/C++, even Purebasic and Powerbasic can do it.
Purebasic includes the binary code with
IncludeBinary "SECUREBEGIN" and the codes are directly inserted at program position.
Powerbasic uses Macros as mentioned above, and Delphi makes
{$I SecureBegin.inc}
{ insert secured code here }
{$I SecureEnd.inc}
just for inspiration to the blitz-team.
Its a really important thing to protect shareware doing this.
Macro SECUREBEGIN = !DB &hEB,&h03,&hD6,&hD6,&h00
Macro SECUREEND = !DB &hEB,&h03,&hD6,&hD6,&hFF
Macros are not really required, its just an example.
Well, it would be nice to insert Opcodes and its an important feature to enable known good protection-systems like Armadillo, Asprotect and the upcoming protections-system from oreans (Themidia or so).
I think all good protectors are needing markers to encrypt data of the code or to NOP it out if a license is missing, so using this technology would be nice. It is available in all known programming-languages. Delphi, C/C++, even Purebasic and Powerbasic can do it.
Purebasic includes the binary code with
IncludeBinary "SECUREBEGIN" and the codes are directly inserted at program position.
Powerbasic uses Macros as mentioned above, and Delphi makes
{$I SecureBegin.inc}
{ insert secured code here }
{$I SecureEnd.inc}
just for inspiration to the blitz-team.
Its a really important thing to protect shareware doing this.