No, it's impossible to recover it - the names of symbols and comments are gone forever. So keep the original version of your code in a safe place!

Yes, protected version of the same symbol will be the same in every file of your project.

If using "shortest" obfuscator (that minimizes total length of identifiers), you will have to reobfuscate entire project and resend all files. In all other cases (e.g. with default obfuscation engine - called "md5") you will have to obfuscate only changed file and to resend only it.

You have to list all functions, variables, names of types from the code you plan to obfuscate that are referenced by calling code as "exceptions". If using Project Manager, put them to Symbols ⇒ User-specified exceptions, if using commandline - put them to file (one per line) and add "-x name-of-file.txt" to your commandline.

No, you will have to list all symbols individually. But you can automate the task of composing such list by the following trick (if using Project Manager): perform obfuscation of your code, go to Symbols ⇒ View resultant symbol mapping, scroll to bottom and click a link "download a list of encountered symbols", save it to some file (getting list of all symbols encountered in your project listed alphabetically), and use your favourite text editor to cut all symbols from that library (since symbols in the file will be sorted alphabetically, all symbols that start from the same string will occur as a single block); copy and paste all "interesting" symbols into Project ⇒ User-specified exceptions.

If using Project Manager, do the following: perform obfuscation of your code, go to Symbols ⇒ View resultant symbol mapping, scroll to bottom and click a link "download a list of encountered symbols", save it to some file (getting list of all symbols encountered in your project listed alphabetically). Paste that list nto Symbols ⇒ "User-specified exceptions". Then go to Symbols ⇒ "User-specified antiexceptions" and list all symbols that need to be obfuscated.

It's impossible to answer this question since the ratio greatly depends on the average length of identifiers, average length of comments and average identation size.

Unfortunately we are not aware of such reviews. Frankly speaking, most of reviews on the net are paid reviews, so even they existed, we wouldn't recommend to trust them. And keep in mind that most reviews a dedicated to a single product, not a comparison of several ones..

We have created some list that can be thought of a comparison "we with others" - just go to product page and scroll to the list of features - all features marked with "unique" are really unique to our product (and are absent in any other).

We recommend you to test our product yourself and make a decision. We have a trial that lets you fully evaluate it and even apply to your project. Such evaluation will reveal all flexibility and power of our product; the only limitation during evaluation is that all symbols can only prefixed with a same prefix. However, this allows to fully evaluate syntax support, support for exceptions, support for javascript embedded into html. Also, projects created during evaluation can be opened by a non-trial version of our product, so you won't waste the time spent during evaluation at all - your product will already be prepared for protection, and applying production-level protection will be a single click on "Build, Rebuild all" in non-trial edition of our product.

With default settings, file is encoded several times after obfuscation. Encoded files require extra time to load first time they are referenced by "use" or "require" statements. This means that encoding decreases only startup time, but not run time. Encoding is an optional stage, it can be turned off or number of encoding iterations can be lowered to reduce startup time increase. Since encoding also increases file size considerably, it can also influence startup time if your project is run from slow media like CD.

Trial version supports only 1 method of symbol name transformation - prepending "ReplacementFor_" to original symbol, while final version has a lot of additional methods (including compression mode achieved by use of 'shortest' obfuscator) that keep symbol length less than 10 characters. Also the trial version of Perl obfuscator adds special block of code to the begining of each file that makes your code expire on a specific date. As a result, the result of obfuscation produced by trial version is much larger than one produced by non-trial version. If encoding is also applied (and, as you remember, it's applied to the result of obfuscation stage), the resultant file size is multiplied even more. And since decoding of smaller file takes less time, the output of trial version starts up slightly slower than output of non-trial version.

Automatic decoding is performed only once at startup, and thus it increases only startup time.

Of course number of encoding iterations applied and size of file affect increase decoding time.

The default value is a recommended value. It's greatly recommended to keep the number of encoding iterations above 4.

Technically it's possible to apply only encoding to the code, without applying obfuscation. Just add '--noparsing' commandline option if not using Project Manager, or put a checkbox "Don't parse source '--noparsing', just encode it" (and a checkbox to the left of it!!) in the Project ⇒ Options, "standard: treat as raw code" mode.

But it is greatly not recommended to apply just encoding since it makes protection of your code much weaker.

You have to read Guide on preparing project for obfuscation and Guide on using Project Manager.

Yes, Stunnix Perl-Obfus is very flexible and advanced product and it can be used for project of any kind and size. It can be used to protect system scripts or daemons, CGI or mod_perl scripts, GUI programs (e.g. ones that use Gtk).

Yes, we will consider adding custom features for additional fee - just contain our sales manager.

No, this doesn't help at all. One pass is enough.

These two interfaces are equal featurewise. So we greatly recommend to use GUI interface (i.e. Project Manager) - it will save the time needed to read manuals, compose commandline etc. Also it allows to protect all files in project in one pass (instead of the need to invoke Stunnix Perl-Obfus from commandline for each file.

Also GUI allows to create buildscripts - Perl scripts that can perform building/clearing output/rebuilding changed files in your project. So once your project options are "stabialized" you will be able to rebuild your entire project (or only changed files) from commandline too.

Stunnix Perl-Obfus is written in Perl programming language.

It is Perl code, but it's protected from analysis and illegal reuse using our perl obfuscation tool - Stunnix Perl-Obfus. We greatly recommend all professional Perl programmers to use it for their projects in order to protect their intellectual property.

Project Manager is in fact a web interface for GUI; when you invoke it it starts Web Server. This allows Project Managerr GUI to work as is on Windows, Unix, MacOS X without any modification. We promote using locally-running webserver as a new effective approach to writing cross-platform GUI, please see more information about Stunnix Perl Web Server on our site.

You probably got an impression that it requires internet connection because your firewall warns that program tries to connect to internet; the firewall you use is incorrect and badly written, address 127.0.0.1 is local; every computer has it as address of itself, independant of the fact whether it's connected to the internet or not. This special address is for special "loopback" network interface card accessible only from the same computer; programs from other computers will even be unable to know that Project Manager and Stunnix Perl Web Server are running and will be unable to communicate with it in any way, so it's safe to run Stunnix Perl Web Server (and Project Manager ) even on computer directly connected to the Internet. But of course Internet connection is not required in order to use Project Manager.

No, Stunnix Perl Web Server by default is configured not to listen on any network interfaces except a special "loopback" interface accessible only from the same computer; programs from other computers will even be unable to know that SPWS is running and will be unable to communicate with it in any way, so it's safe to run Project Manager (and SPWS) even on computer directly connected to the Internet.

First, you have to put exceptions to a file in your project input directory, one symbol per line.

Then you have to create a new mode using Project → Options (using 'BASE' as parent mode for the newly created mode, enter the name of a file with exceptions (there is no need to specify directory name!) into entry (at the bottom of that page) with title "space-separated names of files to get list of exceptions from" and check a checkbox to the left of it (this will mean that the value of this option overrides the value in parent mode), click Save and then go to Project ⇒ Files, put a checkboxes near files you wish these exceptions to be applied to, then select a name of the newly-created mode in the popuplist at the bottom and click Assign processing mode button. Then of course you will have to rebuild the project.

Please do Project, Options and click "Delete project" button.

Please see answer for a related question.

The left checkbox behind some form element in the Project⇒Options specifies whether the value of the option overrides the same value of it from the parent mode (if checked - it overrides, if unchecked - the value of this option from the parent mode is used).
So if the option itself has boolean value, then you see two checkboxes in one line.

Create a file, e.g. named banner.txt with copyright notice inside a comment and save it into project's input directory.

Go to Settings, Edit modes present in the project.., click on "standard: treat as raw code " item in the list, scroll to bottom, in "File-related options " section, find entry "name of file with text to be prepended to the output" put

    banner.txt

into it and put a checkbox to the left of it (IT'S VERY IMPORTANT - this tells that we override the same setting in the parent mode) and click Save.

To export project, open it, then do Project⇒Export as native. What you export this way is a list of files and the options for modes. To import it - just do Project⇒Import.

Project file is stored inside your user's directory - the name of file it's stored in can be seen by going to Project⇒Options (there is a small-printed file location there). You can just copy that file from/to somewhere (and it's OK to rename it, keeping extension).

Also you will have to backup "project state directory" (specified in project⇒options) - it contains exceptions, antiexceptions and symbol mapping information.

Your project (and exported form of it) contains path to the project input, project output and project state directory. If you'll want to relocate these directories to different locations (e.g. after importing project), just go Project⇒Options and edit paths there. Due to this fact it's adviceable to give directories as relative paths relative to project's input directory - this way you'll have less strings to edit when relocating your project.

1. Go to Settings, "Options - locations of dirs, title ..", modify title to something like "new template", click OK.
2. Do Project, "Export for backup (in native format)", save the file you've downloaded to some location.
3. Go to Settings, "Options - locations of dirs, title ..", revert title to original name, click OK (otherwise during next step you'll get 2 projects with same name in Project, Open).
4. Then do Project, "Import from backup", select the file you've saved backup to on a previous step.
5. Go to Project, Open - you'll see project named "new template" in the list, click on it.
6. Go to Settings, "Options - locations of dirs, title ..", put real title and location of input/out/state directories there.
7. Go to Settings, "For files - assign modes to project's files". Click "Select All", click "Stop Managing". This removes all files from the list (you need to do this to get rid of filenames that were present in previous project).
8. Go to Settings, "For files - assign modes to project's files". Click "Select All", click "Add to Project". This will add files in the Input directory to the project; processing mode will be assigned correctly to them.

In order to fix this problem, just turn that line into

eval("use Tk;");

This bug can appear with some other modules too, the way to fix it is the same.

Please see solution in the user's guide.

We've heard only once about such issue. But here is our advice:

Process your code with jamming and encoding disabled. It's better to use Prefix symbol name mangler too.

Then edit the output file, and insert lines like

BEGIN { print STDERR "we are still alive at line " . __LINE__ ."\n"; }

at the top level of the file (i.e. outside all subs) rather often (e.g. on every 1000th line). Then run the script and find the interval of lines it dies on. Insert such BEGIN lines more often inside that interval of lines, to find the line that crashes perl as precisely as possible. Then try to change anything in the lines corresponding to those lines in output file or send us that piece for inspection.

assertions are meant to be non-interactive, since they are executed for each script file (or module) of your project. So if your product has several script files/modules in it, a password will be asked while loading each of the files - so it's a bad idea to add password prompt as a way to check licensing conditions.

You can enable assertion for one of the files though.

First you have to create a new processing mode that will inherrit all settings from "main" mode, but add assertion. To do this, go to Settings, "Edit modes present in the project..,", "Create new mode", give it some title, e.g "files with assertion", specify as parent mode this mode :" standard: treat as raw code",

Then scroll to the group "Ensuring licensing conditions using generic asserters", configure licensing conditions in that section, and put a checkbox near each control there, since otherwise the value of controls will be ignored. Then scroll to the bottom and click Save to complete creation of the new mode.

Then go to Settings, "For files - assign modes to project's files, add/remove files.. ", put a checkbox near file you wish to enable asserters in, and select "files with assertion" from drop down list and click "Assign processing mode".

Create a file named "myasserter.txt" in the project's input directory and fill it with asserter's code. E.g. put code like this into it:

    {#asserter that prevents program from running on Sundays
	use POSIX;
        if ((localtime(time()))[6] == 0) {
            print STDERR "You are not allowed to run this script on Sundays!";
	    #do anything else like deletion of program'siles
            exit 0;#just call exit(0) to break program execution in case of violation
        };
    }

Suppose you wish to enable assertion of licensing conditions for all files in your project. If you wish to enable assertion of licensing conditions only for some files in your project, see question above.

Go to Settings, "Edit modes present in the project..,", click on either the 'standard: treat as raw code' (if enabling assertion for each file) or the mode you've just created as explained in previous question.

Scroll to the group "Ensuring licensing conditions using generic asserters", select "Take code from file" and check a checkbox to the left of this popup list. Put a checkbox to the left of entry "Name of file (relative to project's input directory)" below, and put a name of file "myasserter.txt" in that entry. Then click Save at the bottom of the page.