LangTu Posted March 27, 2009 Share Posted March 27, 2009 (edited) <Removed> Edited April 8, 2009 by Valik Link to comment Share on other sites More sharing options...
=sinister= Posted April 8, 2009 Share Posted April 8, 2009 (edited) Hmm ok myAutoToExe is finding this signature: <Removed>. If someone can change this signature, myAutToExe won't be able to decompile the script. But when you change this, AutoIt throws an error?? Edited April 8, 2009 by Valik Link to comment Share on other sites More sharing options...
Skrip Posted April 8, 2009 Share Posted April 8, 2009 (edited) Hmm ok myAutoToExe is finding this signature: <Removed>. If someone can change this signature, myAutToExe won't be able to decompile the script. But when you change this, AutoIt throws an error??might want to say what error... Edited April 8, 2009 by Valik [left][sub]We're trapped in the belly of this horrible machine.[/sub][sup]And the machine is bleeding to death...[/sup][sup][/sup][/left] Link to comment Share on other sites More sharing options...
=sinister= Posted April 8, 2009 Share Posted April 8, 2009 It was like "Cant find start/stop of compiled script. Ill check when i get home. But i know someone who has protected his autoit exe's and it has every other autoit sig but not this one. Link to comment Share on other sites More sharing options...
Valik Posted April 8, 2009 Share Posted April 8, 2009 This script is a violation of the AutoIt license. I have removed the offending content and locked this thread. Keep in mind that if you are using this you are violating the AutoIt license. Link to comment Share on other sites More sharing options...
Valik Posted April 9, 2009 Share Posted April 9, 2009 I was asked how w0uter's script breaks the license. It's this clause which you can read for yourself in the 3.3.0.0 documentation:Reverse engineering. You may not reverse engineer or disassemble the SOFTWARE PRODUCT or compiled scripts that were created with the SOFTWARE PRODUCT.In order to defeat the decompilers that are out there, w0uter (and others with similar tools) must figure out how we store the script. Then they must figure out how to break the decompiler while not breaking AutoIt. This requires figuring out how AutoIt works, also known as reverse engineering. Since we have a "you may not reverse engineer" clause in our license we certainly can't allow something to flagrantly violate it.Before somebody else asks, the reason I closed this even though it's something of a white-hat effort is where do we draw the line? The same technique (reverse engineering) that's used to create a too like w0uter made is the same technique used to create a decompiler. Both are violations of the license. The distinction many of us want to make is that this should be allowed because it's "helping". The counter argument to that, however, is that some people think a decompiler is "helping". If you get the right two groups of people you can let them argue and they will say the exact same thing about the validity of both decompilers and anti-decompilers. But the fundamental point, and the reason this thread was closed, is that both tools, no matter which color hat you think they wear, violate the license agreement concerning reverse engineering. Link to comment Share on other sites More sharing options...
Recommended Posts