Jump to content

Recommended Posts

Posted (edited)

Perhaps a compromise something like this would achieve your goal.

pseudocode:

$var = "MsgBox(0,'Title','Text')"
$TempFile = _TempFile(@TempDir, "~", ".au3")
_FileWrite ( $TempFile, $var )
RunWait('Auto2Exe /in '  & $TempFile)
FileDelete($TempFile)
Edited by Bowmore

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to build bigger and better idiots. So far, the universe is winning."- Rick Cook

Posted

Perhaps a compromise something like this would achieve your goal.

pseudocode:

$var = "MsgBox(0,'Title','Text')"
$TempFile = _TempFile(@TempDir, "~", ".au3")
_FileWrite ( $TempFile, $var )
RunWait('Auto2Exe /in '  & $TempFile)
FileDelete($TempFile)
That's exactly what i'm trying to avoid.

If someone were to stop the script after the file write, it would be giving away the source code!

tolle indicium

Posted

You know that if you are trying to protect your AutoIt source from users who want it, you are going to fail, right? There have been numerous decompilers that a user could easily use (not that I promote this).

So, I should just make it easier for them??

-.-

tolle indicium

Posted

No, I'm just saying that if it is so much trouble, you might as well not try. They'll get it anyways.

I just don't want people to accidentally get the source, say the power goes out and it doesn't get to delete the file.

then they reopen the folder find this random file and read the source and steal!

If it's obfuscated at least they can't easily read it, a skiddie would have to get an autoit decompiler instead of just reading it!

It's worth keeping my script away from anyone just reading it, I don't want to make half ass programs, if there's something I can do about this, I should at least try.

tolle indicium

  • Developers
Posted

There's a utility that compiles variables?

Where is this located? I've never heard of it!

Unless there's a utility in Obfuscator that compiles parameters? (obfuscator.exe -$compilevariable) ?

I'm looking for the documentation for Obfuscator right now, and I don't see anything...

http://www.autoitscript.com/autoit3/scite/...uscator_doc.htm

These is no such option as that would not work due to the commandline limitations.

SciTE4AutoIt3 Full installer Download page   - Beta files       Read before posting     How to post scriptsource   Forum etiquette  Forum Rules 
 
Live for the present,
Dream of the future,
Learn from the past.
  :)

Posted

Could you not obfuscate the file but leave some of it unobfuscated?

there are some options

#Obfuscator_Ignore_Funcs

#Obfuscator_Ignore_Variables

#Obfuscator_Parameters

but I'm not entirely sure if I have got it right, but the parts \ variables that need changing could be moved to a function that is not obfuscated, the rest of the code is already obfuscated and the only bits with text are in the functions.

Or if that doesn't/Wont work. Can you have an obfuscated file then use a #include to include an unobfuscated file with the variable data that once compiled it all goes together? That way there won't be much for the user to see if ever a files were left behind.

  • Developers
Posted

His issue is that he doesn't want to write the generated script to a file first, probably worried about making it easy to find it and retrieve the original code.

SciTE4AutoIt3 Full installer Download page   - Beta files       Read before posting     How to post scriptsource   Forum etiquette  Forum Rules 
 
Live for the present,
Dream of the future,
Learn from the past.
  :)

Posted
Posted

Could you not obfuscate the file but leave some of it unobfuscated?

there are some options

#Obfuscator_Ignore_Funcs

#Obfuscator_Ignore_Variables

#Obfuscator_Parameters

but I'm not entirely sure if I have got it right, but the parts \ variables that need changing could be moved to a function that is not obfuscated, the rest of the code is already obfuscated and the only bits with text are in the functions.

Or if that doesn't/Wont work. Can you have an obfuscated file then use a #include to include an unobfuscated file with the variable data that once compiled it all goes together? That way there won't be much for the user to see if ever a files were left behind.

That's an amazing idea!!!

I didnt even think of that!

thank you! you have solved my problem. ;)

tolle indicium

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...