Obfuscator (discontinued)

[Jos]

Hi,

first of all! Great! And great idea to include it in Scite!

There is a problem with äüö in e.g. names of buttons.

So long,

Mega

Could you give me a simple scriplet to test with so I know for sure I am looking at the right thing ?

Please try v 0.0.0.29 to see if that fixes it .....

Edited April 9, 2007 by JdeB

[Jon]

Very cool, JdeB

[Xenobiologist]

Hi,

no problem:

#include <GUIConstants.au3>
Global $text = ' ü ö ä  | ³{[] }\ß µ ,-~ö<>^ ^  '
GUICreate($text)
GUICtrlCreateButton($text, 10, 50, 150)
GUICtrlCreateLabel($text, 10, 150, 150)
GUISetState (@SW_SHOW)   
While 1
    $msg = GUIGetMsg()
    
    If $msg = $GUI_EVENT_CLOSE Then ExitLoop
Wend

Edit: Okay, I check the new version.

Edit 2: Yes, you did it again. :-) Firstly in Scite and now in your cool Obfuscator! Besides it is th.meger

So long,

Mega

Edited April 9, 2007 by th.meger

[big_daddy]

Great work Jos!

I'm guessing this should only pertain to the AutoIt Execute() Function and not objects?

-> ### Obfuscation Warning: Found Execute() statement which could lead to problems running your obfuscated script.

-> ### current Func:_WordDocFindReplace

Here's the section of code...

$o_Find = $v_SearchRange.Find
With $o_Find
    .ClearFormatting ()
    .Replacement.ClearFormatting ()
    $return = .Execute ($s_FindText, $f_MatchCase, $f_MatchWholeWord, $f_MatchWildcards, $f_MatchSoundsLike, _
            $f_MatchAllWordForms, $f_Forward, $i_Wrap, $f_Format, $s_ReplaceWith, $i_Replace)
EndWith

[Jos]

Great work Jos!

I'm guessing this should only pertain to the AutoIt Execute() Function and not objects?

Here's the section of code...

$o_Find = $v_SearchRange.Find
With $o_Find
    .ClearFormatting ()
    .Replacement.ClearFormatting ()
    $return = .Execute ($s_FindText, $f_MatchCase, $f_MatchWholeWord, $f_MatchWildcards, $f_MatchSoundsLike, _
            $f_MatchAllWordForms, $f_Forward, $i_Wrap, $f_Format, $s_ReplaceWith, $i_Replace)
EndWith

Added for the next version a test to check for .Execute.

Thanks

Edit: Updated in ver 0.0.0.30

Edited April 9, 2007 by JdeB

[Valuater]

Just as suggestions....

1

The file Program.au3 when obfuscated will be Program_Obfuscated.au3. If Program_Obfuscated.au3 already exists, it will be over-written without notification

2

notify with option to remove "unused" functions?? ( helps with file size )

Thanks for a great and useful tool!!

8)

Edited April 9, 2007 by Valuater

[faldo]

I just wanted to extend a million thanks for this program, JdeB.

Not a single error when used with a 3562 line long script of mine, exelent work!

I've been crying blood since Smoke_N got mad and left us all to out fate, you're my new hero

[Jos]

Just as suggestions....

1

The file Program.au3 when obfuscated will be Program_Obfuscated.au3. If Program_Obfuscated.au3 already exists, it will be over-written without notification

2

notify with option to remove "unused" functions?? ( helps with file size )

Thanks for a great and useful tool!!

8)

1. The plan is to incorporate it into SciTE so I wanted to give it a fixed "obvious" name that shouldn't be a problem. I do not want it to prompt or anything, but just override it with the latest version.

2. No going down that road. It is much too risky to mess up things. ... Its already difficult as it is to generate a working script Obfuscator.

[Jos]

Made some changes to the String encryption logic to speed it up..

Please have a go with the latest version to see if I broke anything.

v0.0.0.30: Fixed warnings for Comobj.execute. . (tnx big_daddy)

v0.0.0.30: Change String encrypt/decrypt logic to speed up the decryption process by caching information.

[Blackstar]

Where did you see that at?

[Blackstar]

Oh JdeB, can you please add version number in your latest compiled program or in the zip file name when you plan to release it in public? I didn't realized you released like 2 or 3 versions in last 24 hours when i first downloaded your high tech obfuscation program. Yeah you can get the right click properties on obfuscater.exe file to get the version but we don't need to drill down to get that version number. thanks!

EDIT:

Just ran your program on my nearly 4000 lines of code and they all works. good job! Will test some more scripts to find any bugs...

Edited April 10, 2007 by Blackstar

[WeMartiansAreFriendly]

wow, didnt expect this.. nice job, whats amazing is how autoit treats, and understands all that jibberish that is outputed.. lol

[Kickassjoe]

What She said! Great job!

When do you think it will be implemented into Scite?

[Jos]

Oh JdeB, can you please add version number in your latest compiled program or in the zip file name when you plan to release it in public? I didn't realized you released like 2 or 3 versions in last 24 hours when i first downloaded your high tech obfuscation program. Yeah you can get the right click properties on obfuscater.exe file to get the version but we don't need to drill down to get that version number. thanks!

EDIT:

Just ran your program on my nearly 4000 lines of code and they all works. good job! Will test some more scripts to find any bugs...

Have you checked both the Resource of the program and the Obfuscator.log ?

You can also see it in the statusbar when you are in explorer and selected the file.

They both have the current version number, or am I missing your point ?

Edited April 10, 2007 by JdeB

[Xenobiologist]

Hi,

there is a small bug converting this:

Func Speak($Text, $Rate, $Vol)
    $voice.Rate = $Rate
    $voice.Volume = $Vol
    $voice.Speak ($Text)
EndFunc   ;==>Speak

It converts Speak

So long,

Mega

[GaryFrost]

Hi,

there is a small bug converting this:

Func Speak($Text, $Rate, $Vol)
    $voice.Rate = $Rate
    $voice.Volume = $Vol
    $voice.Speak ($Text)
EndFunc   ;==>Speak

It converts Speak

So long,

Mega

This is the same issue that encodeit had. I would suggest changing the name of the function, add an _ to front of it.

[Jos]

This is the same issue that encodeit had. I would suggest changing the name of the function, add an _ to front of it.

Will be fixed in the next version..

[Xenobiologist]

Will be fixed in the next version..

Hi,

nice! Thanks!

I have some more:

1. Where is the #Region Compiler directives section gone?

2. It would be nice to have something like #os #oe to exclude some things like the header of a script or some comments.

So long,

Mega

[Jos]

Hi,

nice! Thanks!

I have some more:

1. Where is the #Region Compiler directives section gone?

2. It would be nice to have something like #os #oe to exclude some things like the header of a script or some comments.

So long,

Mega

My approach to this is to make the obfuscated source as "unreadable" as possible, so it strips all formatting, Comment, Compiler Directives etc .

Would you agree that this should be the goal and thus not leave anything in there as "markers"?

Edit: With the AutoIt3Wrapper integration, the directives are read and use on the obfuscated compiled version, so they are not needed in the obfuscated source.

Edited April 10, 2007 by JdeB

[Xenobiologist]

My approach to this is to make the obfuscated source as "unreadable" as possible, so it strips all formatting, Comment, Compiler Directives etc .

Would you agree that this should be the goal and thus not leave anything in there as "markers"?

Edit: With the AutoIt3Wrapper integration, the directives are read and use on the obfuscated compiled version, so they are not needed in the obfuscated source.

Hi,

yes I agree with you. But I'd prefer to have an option to exclude code from stripping or obfuscating. Something like a warning. --> This code is obfuscated and written by ...

Or you cracked the exe, but know have fun with this hardly readable code! :-)

Maybe the easiest way would be a keyword for the obfuscator start at this line #obfuscatorOn# so that I can put readable information on top of the script.

Same thing with lines in the code, (comments no really Autoit code), but is nice to have! :-)

So, what do you think?

So long,

Mega