How do I remove MSIL from my native executable?

  • Thread starter Number 11950 - GPEMC! Replace number with 11950
  • Start date
N

Number 11950 - GPEMC! Replace number with 11950

[SNIP]
Maybe this will be of interest:
[SNIP]

Thank you Chris, I have had a look. It's inspiring to say the least,
although diagramatic representation(?) of an obfuscation technique without
the textual explanation seems a bit unusual.

There has been a start to this with the definition of specific "Setup"
behaviours in VB2005 - however, program behaviour also needs to be modified
in trial versions necessitating either a component or wrapper.

One of the problems with encrypted code is that it winds up decrypted in
memory somewhere, and knowing virtual memory, somewhere on the disk as well.
This is what happens to served material that's run client side but
"protected" - just sitting in a temporary directory - a potential issue with
SAAS based approached to IP protection.

I plan to run a pilot study on respective conversion rates of straight
versus obfuscated trial locking mechanism, using a simplified application
based purchasing system in otherwise identical products referenced at
random. I'll publish the results on my site when the study hits three
months, probably early January next year...

Anyway, I've sent Microsoft an email to see where they are at with SLP.

Thanks again...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top