Jump to content
Sign in to follow this  
Guest drei3

Reverse engineering compiled scripts

Recommended Posts

Guest drei3

the encryption is two-way.  For this reason you should regard the compiled exe as being encoded rather than completely safe.

This is the only thing I've found regarding the subject stated by the devs. There is an option that can disallow decompilation. When this option is used is it well protected against reverse engineering the .exe? I am afraid to make one of my compiled autoit scripts public because I don't want the source stolen. What sort of protection is offered with the compiler, and is there anything further I can do that works under the GNU and will make my .exe safer?

Thank you Jon and the entire AutoIt team for an amazing program.

Share this post


Link to post
Share on other sites

This is the only thing I've found regarding the subject stated by the devs.  There is an option that can disallow decompilation.  When this option is used is it well protected against reverse engineering the .exe?  I am afraid to make one of my compiled autoit scripts public because I don't want the source stolen.  What sort of protection is offered with the compiler, and is there anything further I can do that works under the GNU and will make my .exe safer?

Thank you Jon and the entire AutoIt team for an amazing program.

<{POST_SNAPBACK}>

The decompilation could be accomplished with brute force, I'm sure. But the longer your password is, the more secure the encryption is. Now, with that being said, I'm sure one could attempt to reverse engineer what will always be encoded the same way every time, the stub that contains the dencryption engine.

Lofting the cyberwinds on teknoleather wings, I am...The Blue Drache

Share this post


Link to post
Share on other sites
Guest drei3

The decompilation could be accomplished with brute force, I'm sure.  But the longer your password is, the more secure the encryption is.  Now, with that being said, I'm sure one could attempt to reverse engineer what will always be encoded the same way every time, the stub that contains the dencryption engine.

<{POST_SNAPBACK}>

If I were to use a password compilation, I would make the password 20+ characters for sure. My question was more about the option of disallowing decompilation which will not allow you to set a decompilation password.

Share this post


Link to post
Share on other sites
Guest drei3

Check jon's post here

<{POST_SNAPBACK}>

Thanks very much

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...