256 encryption

dghundt · Post by **dghundt** » Sat Aug 05, 2006 9:25 am

I am trying to find out a little more about what your 256 encryption feature does.

Are the executable files encryped after one installs the application?
Does this mean that if I have a licensing class in my program it would be very difficult to determine the hash algorithm I use including the salt?

Thanks

CandiceJones · Post by **CandiceJones** » Sat Aug 05, 2006 12:34 pm

The encryption is used to encrypt your entire setup payload. When your program files are installed, they are not encrypted, they are normal files.

dghundt · Post by **dghundt** » Sat Aug 05, 2006 10:46 pm

thanks candice.

does this mean that my installed executable can therefore be easily reverse engineered?

what is the benefit of encrypting the setup payload itself?

david

CandiceJones · Post by **CandiceJones** » Sun Aug 06, 2006 7:32 am

The benefit of encrypting the setup payload is preventing access to your binaries if an end-user does not know the password.

The ease of reverse engineering for your installed files depends on the programming languages, methodologies, and anti-piracy tools you used when building your product.