Navutilus Object Squeeze DEMO
Optimize (Squeeze) Navision objects. Make them impenetrable & small. Protect source code.
Navutilus Object Squeeze can be useful for:
- Protected demo-version creation
- Protection of your active database objects from unintentional or/and unauthorized modifications
- Protection of the crucial/complex objects against unreasonable modifications
- Know-how protection ( e.g. by "hiding" it between the functions of some codeunits)
We thoroughly tested the squeeze-technology with all recent Microsoft Dynamics NAV versions.
The majority of Navutilus objects are squeezed.
Technical Spec
Release: 1.00
Release date: 16-September-2009
Microsoft Dynamics NAV Version: 4.xx, 5.xx, 2009
Microsoft Dynamics NAV Database: Native, MS SQL
Content Spec: 2 tables, 3 forms, 2 codeunits
Product Spec
- Squeezes any objects with Navision license permissions to read and modify
- Squeezes really large objects
- Replaces Source Code with text Option
- Replaces Locals' Names with text Option
- Replaces Documentation trigger with text Option
- Replaces Source triggers with text Option
- Stores and Maintains Squeeze Sets of Objects
- Squeezed object types: Tables, Form, Reports, Dataports, XMLports, Codeunits
- Makes Objects smaller (by up to 50%)
http://www.mibuso.com/dlinfo.asp?FileID=1162
Discuss this download here.
Comments
TVision Technology Ltd
Not yet
On top of this I would like to warn all Navision end users. Make certain in you contract with your partner to have a clear clause that makes certain that your partner will never use BLACKMAILING code like this to force you to never be able to change partners. Be very aware that if your partner locks code using tools like this, that they can then charge you anything they want for support, since there is no way you can ever go to another partner for support.
Partners that lock objects using illegal hacks like this should not be supporting customers. If your partner is using techniques like this to lock you ito them, the name and shame to protect other customers.
One of the strengths of Navision has always been its openness. Once we start to lock code and prevent customers to be able to get support we revert to the dark ages.
PLEASE do not support this company. And do not ever purchase Add-Ons that have been encrypted using such tools.
:thumbsdown:
TVision Technology Ltd
Except, David, in many countries that clause is either illegal or could very easily be found to be "unreasonable" or to not apply to working out how Navision objects are compiled. The reasoning behind the latter point is that at no point are you taking object code that you have to create the original source that you don't. (the definition of 'reverse engineering' in this case) This is especially true as this is a 'dictated' contract where the 'partner' has basically no chance to disagree any specific terms.
In addition, even if the contact term is valid it doesn't make the code "illegal" it just makes the production of it a "breach of contract" for someone who's currently signed as a partner. NB Please don't try to switch to EULAs, in most places they're a smelly joke.
Other than that I agree with you David, when any partner or addin maker uses this stuff you have to wonder what they're hiding, or why they don't trust you to abide by your contract with them or even copyright law. Or maybe the code they're hiding is so bad even they are embarrassed by it; and when they add extra license keys too ...
makes you wonder.
It also makes you remember you don't have a 'reverse engineering' contract with them, or at least your mate down the road doesn't.
TVision Technology Ltd
Optimize (Squeeze) Navision objects. Make them impenetrable & small. Protect source code.
Demo restrictions:
- Only object IDs 1-100 are processing
Navutilus Object Squeeze can be useful for:
- Protected demo-version creation
- Protection of your active database objects from unintentional or/and unauthorized modifications
- Protection of the crucial/complex objects against unreasonable modifications
- Know-how protection ( e.g. by "hiding" it between the functions of some codeunits)
We thoroughly tested the squeeze-technology with all recent Microsoft Dynamics NAV versions.
The majority of Navutilus objects are squeezed.
Technical Spec
Release: 1.00
Release date: 16-September-2009
Microsoft Dynamics NAV Version: 4.xx, 5.xx, 2009
Microsoft Dynamics NAV Database: Native, MS SQL
Content Spec: 2 tables, 3 forms, 2 codeunits
Product Spec
- Squeezes any objects with Navision license permissions to read and modify
- Squeezes really large objects
- Replaces Source Code with text Option
- Replaces Locals' Names with text Option
- Replaces Documentation trigger with text Option
- Replaces Source triggers with text Option
- Stores and Maintains Squeeze Sets of Objects
- Squeezed object types: Tables, Form, Reports, Dataports, XMLports, Codeunits
- Makes Objects smaller (by up to 50%)
http://www.mibuso.com/dlinfo.asp?FileID=1162
Discuss this download here.
I seriously doubt that partners are interested in total code closure - it would be very weak move in competitive environment... And what would be the purpose of that total closure? It would have to be well justified - otherwise one could ruin management of the project, I think... Do You really have an evidence? Are You really able to prove? Then do it - without that kind of emotions... Oh, yes! I'd been eating that kind of stuff almost for 9 years... Unfortunately, it isn't that open - You know it quite well, I suppose... Exactly. You're absolutely right. I can add only this: we are still living there! Look: do You really want to state, that source code openness is enough for considerable freedom of choice for us? And what about proper level of partner expertise, needed for secure partner change? What about proper programming discipline, what about various methodologies (used by various partners)... and so on? There's no even a smell of perfect competition in this industry, You know it quite well, I suppose... So it is not the code openness that rules - standards (including those of partners' competence) much more important!
I went through partner change with highly customised solution (large one!) in my hands... It was not a real pleasure, I can assure You! "You have all C/AL codes on hand, what are your problems? - Won't you read all those thousands lines by yourself? Do you really think we can read/understand this so easily? It is not the way we do our programming..." - and I understand them - they were different...
As for code openness as MS Partner's duty - let me remind You, that it is not only "dark age" we are living through, but also age of intellectual property protection. And I perfectly understand those professionals, that (like myself - in my area) concerned about copyrights, trademark protection etc. As for software - there's a vast range of restrictions - from GNU GPL and OSI to Adobe, Autodesk and IBM, and... One can choose his own style to his one taste
Regards
RIS Plus, LLC
Optimize (Squeeze) Navision objects. Make them impenetrable & small. Protect source code.
ATTENTION!
Demo restrictions:
- only object IDs 1-100 are processing
- only 4 first function triggers are processing
- "Erase Locals' Names" function is not accessible
The utility won't process the object without license permissions to read and modify.
PLEASE DO NOT FORGET TO BACKUP YOUR OBJECTS BEFORE PROCESSING THEM.
Navutilus Object Squeeze can be useful for:
- Protected demo-version creation
- Protection of your active database objects from unintentional or/and unauthorized modifications
- Protection of the crucial/complex objects against unreasonable modifications
- Know-how protection ( e.g. by "hiding" it between the functions of some codeunits)
We thoroughly tested the squeeze-technology with all recent Microsoft Dynamics NAV versions.
The majority of Navutilus objects are squeezed.
Technical Spec
Release: 1.00
Release date: 16-September-2009
Microsoft Dynamics NAV Version: 4.xx, 5.xx, 2009
Microsoft Dynamics NAV Database: Native, MS SQL
Content Spec: 2 tables, 3 forms, 2 codeunits
Product Spec
- Squeezes any objects with Navision license permissions to read and modify
- Squeezes really large objects
- Replaces Source Code with text Option
- Replaces Locals' Names with text Option
- Replaces Documentation trigger with text Option
- Replaces Source triggers with text Option
- Stores and Maintains Squeeze Sets of Objects
- Squeezed object types: Tables, Form, Reports, Dataports, XMLports, Codeunits
- Makes Objects smaller (by up to 50%)
http://www.mibuso.com/dlinfo.asp?FileID=1162
Discuss this download here.
"Never memorize what you can easily find in a book".....Or Mibuso
My Blog
Just interesting,
Can anybody tell me how object squeeze is done?
They change text of object code to bytes?
And import it in “Blob Reference” field of Object table?
But how only several functions not all object are squeezed?
And instead of code in triggers there is only “ www.blabla.com “?
I just want to know a little bit more about such a possibility. Is any special structure, how Navision understands it?
Thank you.
Optimize (Squeeze) Navision objects. Make them impenetrable & small. Protect source code.
ATTENTION!
Demo restrictions:
- only object IDs 1-100 are processing
The utility won't process the object without license permissions to read and modify.
PLEASE DO NOT FORGET TO BACKUP YOUR OBJECTS BEFORE PROCESSING THEM.
Version 1.02 new:
- Erase Globals' Names with text Option
- Erase Functions' Names with text Option
Navutilus Object Squeeze can be useful for:
- Protected demo-version creation
- Protection of your active database objects from unintentional or/and unauthorized modifications
- Protection of the crucial/complex objects against unreasonable modifications
- Know-how protection ( e.g. by "hiding" it between the functions of some codeunits)
We thoroughly tested the squeeze-technology with all recent Microsoft Dynamics NAV versions.
The majority of Navutilus objects are squeezed.
Technical Spec
Release: 1.02
Release date: 05-February-2010
Microsoft Dynamics NAV Version: 4.xx, 5.xx, 2009
Microsoft Dynamics NAV Database: Native, MS SQL
Content Spec: 2 tables, 3 forms, 2 codeunits
Product Spec
- Squeezes any objects with Navision license permissions to read and modify
- Squeezes really large objects
- Replaces Source Code with text Option
- Replaces Locals' Names with text Option
- Replaces Documentation trigger with text Option
- Replaces Source triggers with text Option
- Stores and Maintains Squeeze Sets of Objects
- Squeezed object types: Tables, Form, Reports, Dataports, XMLports, Codeunits
- Makes Objects smaller (by up to 50%)
http://www.mibuso.com/dlinfo.asp?FileID=1162
Discuss this download here.
Optimize (Squeeze) Navision objects. Make them impenetrable & small. Protect source code.
ATTENTION!
Demo restrictions:
- only object IDs 1-100 are processing
The utility won't process the object without license permissions to read and modify.
PLEASE DO NOT FORGET TO BACKUP YOUR OBJECTS BEFORE PROCESSING THEM.
Version 1.02 new:
- Erase Globals' Names Option
- Erase Functions' Names Option
Navutilus Object Squeeze can be useful for:
- Protected demo-version creation
- Protection of your active database objects from unintentional or/and unauthorized modifications
- Protection of the crucial/complex objects against unreasonable modifications
- Know-how protection ( e.g. by "hiding" it between the functions of some codeunits)
We thoroughly tested the squeeze-technology with all recent Microsoft Dynamics NAV versions.
The majority of Navutilus objects are squeezed.
Technical Spec
Release: 1.02
Release date: 05-February-2010
Microsoft Dynamics NAV Version: 4.xx, 5.xx, 2009
Microsoft Dynamics NAV Database: Native, MS SQL
Content Spec: 2 tables, 3 forms, 2 codeunits
Product Spec
- Squeezes any objects with Navision license permissions to read and modify
- Squeezes really large objects
- Erases Locals' Names
- Erases Globals' Names
- Erases Functions' Names
- Replaces Documentation trigger with text
- Replaces Source triggers with text
- Stores and Maintains Squeeze Sets of Objects
- Squeezed object types: Tables, Form, Reports, Dataports, XMLports, Codeunits
- Makes Objects smaller (by up to 50%)
http://www.mibuso.com/dlinfo.asp?FileID=1162
Discuss this download here.
Optimize (Squeeze) Navision objects. Make them impenetrable & small. Protect source code.
ATTENTION!
Demo restrictions:
- only object IDs 1-100 are processing
The utility won't process the object without license permissions to read and modify.
PLEASE DO NOT FORGET TO BACKUP YOUR OBJECTS BEFORE PROCESSING THEM.
Version 1.03 new:
- Temporary tables squeeze problem solved
Version 1.02 new:
- Erase Globals' Names Option
- Erase Functions' Names Option
Navutilus Object Squeeze can be useful for:
- Protected demo-version creation
- Protection of your active database objects from unintentional or/and unauthorized modifications
- Protection of the crucial/complex objects against unreasonable modifications
- Know-how protection ( e.g. by "hiding" it between the functions of some codeunits)
We thoroughly tested the squeeze-technology with all recent Microsoft Dynamics NAV versions.
The majority of Navutilus objects are squeezed.
Technical Spec
Release: 1.03
Release date: 14-April-2011
Microsoft Dynamics NAV Version: 4.xx, 5.xx, 2009
Microsoft Dynamics NAV Database: Native, MS SQL
Content Spec: 2 tables, 3 forms, 2 codeunits
Product Spec
- Squeezes any objects with Navision license permissions to read and modify
- Squeezes really large objects
- Erases Locals' Names
- Erases Globals' Names
- Erases Functions' Names
- Replaces Documentation trigger with text
- Replaces Source triggers with text
- Stores and Maintains Squeeze Sets of Objects
- Squeezed object types: Tables, Form, Reports, Dataports, XMLports, Codeunits
- Makes Objects smaller (by up to 50%)
http://www.mibuso.com/dlinfo.asp?FileID=1162
Discuss this download here.
I see two sides of the coin. On the one hand this is a way to protect your source code, on the other hand your objects will be irreversible changed. This is a big danger.
(I don't know enough about Microsoft's contracts to decide if David's post is also an issue. But as far as I know David he's one of the best NAV specialists in the world, so I would trust his word.)
I have created some code which took me days to create. And now a partner is using this also. Next time I will protect my code changes. Not all source code but only libraries and processes. If hope this tool works in NAV 2009 R2? Can this be confirmed?
We made some addons to their system, but the previous partner had put some licensing checking code in their modification and squeezed it.
We couldn't implement our modification, because when we changed the license to include our tables and forms, the old modification caused an error, because the license had been changed.
THAT is blackmail. Or at least a hostage situation.
If a squeezed object is re-compiled, it loses all its functionality(!). Even if you have a backup of the database,
you can't export objects from the backup and import it to the production database, because the objects doesn't contain any source code.
The only way would be to backup all the data, restore to the backup database, and then import the data.