Add an obfuscator option lease

Scriptcase 8 Suggestions
#1

In the Publish option please add an “obfuscate” (yes/no) option then scriptcase generate all the .php files previously obfuscated and then zip the folder to publish

thanks
aquiles

#2

I don’t think NetMake has to spend time on this. If you want to obfuscate/encrypt the generated code, you can use Zend guard, source guardian, and so on. I mean, if there is a feature for this great, but I think there are more important bugs/new features to do than this.

Generated code is a hell btw, its obfuscated itself lol

#3

Hah! Funny Giu :slight_smile:

#4

exactly Guiseppe, “You Don’t Think”
BUT What if “many think” it would be beneficial to protect the code without paying for Zend Guard ??

greetings
aquiles

#5

http://www.phpprotect.info that should do it.
Basically you can base64 encode your code (or use any other encoding) and change all your php code to eval(base64_decode("your encoded string here… "));

Alternatively you could use turk mmcache (I havent used it yet).

#6

[QUOTE=aquiles;38387]exactly Guiseppe, “You Don’t Think”
BUT What if “many think” it would be beneficial to protect the code without paying for Zend Guard ??

greetings
aquiles[/QUOTE]

Then you have to pay to NetMake for this effort, and its better each company do what’s best knows to do. SC is not a an ofuscator tool, and their team, maybe, doesn’t has experience in this task.

Don’t misunderstand me, I will love to have this feature, but we must be realistic. Its more important bug fixing and a lot of features related to what SC does, instead code protection, for various reasons.

  • SC team doesnt has probably experience in this task.
  • There are important bugs and features must be implemented ASAP.
  • SC generated code is the real hell. In Portuguese and without reusing code.
  • Sourceguardian just costs 150$ I think.

If you want to protect your code, what do you prefer, a well protection or basic protection?

Just my opnion. I repeat, I would like this feature btw.

#7

Its a good idea in general, encrypting is not a problem, but a feature likes this demand quite some time.
We might implement this but only for future version, I’ll keep this in mind when we start to discuss the next features our tool will provide.

Thanks for the feedback.

Hahaha, in my defense. There is a lot of old scriptcase code (from old newbies programmers). There are things that I see… and it burns my eyes…

BUT, we’re always reworking old code here (for the sake of performance!!) - wich generates some bugs sometimes, but belive me, we try very hard to catch all this bugs when we rework something.
And its great for everyone.

#8

[QUOTE=Cavadinha;38909]Its a good idea in general, encrypting is not a problem, but a feature likes this demand quite some time.
We might implement this but only for future version, I’ll keep this in mind when we start to discuss the next features our tool will provide.

Thanks for the feedback.

Hahaha, in my defense. There is a lot of old scriptcase code (from old newbies programmers). There are things that I see… and it burns my eyes…

BUT, we’re always reworking old code here (for the sake of performance!!) - wich generates some bugs sometimes, but belive me, we try very hard to catch all this bugs when we rework something.
And its great for everyone.[/QUOTE]

Just some letters out there… O.O.P
:smiley: