How to encrypt the NAV table code?

kish2007

Hi Guys,
Can u guide me how can i encrypt or block the code. If somebody go to the Table design and if they opened the C/AL code then the code should not be visible.

Is it possible in NAV????

Waiting for ur valuable replies....


Regards,
Kishore.

Luc_VanDyck

Why shouldn't the code be visible?

kish2007

because coding should not see some other person. This is for security purpose.
Is it possible.

Luc_VanDyck

Security by obscurity is never a good protection system.

I'm not gonna help you with this one, as I'm against this kind of practices in the NAV channel.

Sog

sure, the code is not visible if they do not have the rights to view it.
The licence is enough protection for code.
If other people have the developer license (or .. or .. with the rights to view code)
then you shouldn't have any problem because you know they have enough experience not to mess with it.
If you want your code not to be seen by developers, then you have to send it to MS for review, so it can be a certified add-on and will fall in the range that developers are not able to view.

David_Singleton

This is a very simple problem to solve. If someone has access to the code and you don't want to let them change the code, then either remove their access or sack them.

David_Singleton

Luc Van Dyck wrote:

Security by obscurity is never a good protection system.

I'm not gonna help you with this one, as I'm against this kind of practices in the NAV channel.

=D>

And I agree 100% with Luc.

Dirk.Fischer

I'm currently working in a project where the NSC works with some kind of Source Code Removal Tool - It's horror as you are no longer able to debug - I agree with the others that this should never be the way.

David_Singleton

Dirk.Fischer wrote:

I'm currently working in a project where the NSC works with some kind of Source Code Removal Tool - It's horror as you are no longer able to debug - I agree with the others that this should never be the way.

Suggest to the customer that they sue the NSC to get access to the source code, since if they were charged time and materials to develop code, they own it. Then change to a partner that is honest.

Also a warning to new Navision customers. Make sure there is a clause in your contract that says the partner MUST give you source code for all work they do, other wise they will be able to control you and you will not be able to change partners.

matttrax

David Singleton wrote:

Suggest to the customer that they sue the NSC to get access to the source code, since if they were charged time and materials to develop code, they own it. Then change to a partner that is honest.

Also a warning to new Navision customers. Make sure there is a clause in your contract that says the partner MUST give you source code for all work they do, other wise they will be able to control you and you will not be able to change partners.

=D>

kish2007 wrote:

because coding should not see some other person. This is for security purpose.

NAV is Open Source for those customers and partners who pay for it. If you do not like that then develop for a closed-source system. If I shelled out $40,000 for Application Builder and Solution Designer in my license and then found out I couldn't view the code because my NSC had hidden it I would sue the crap out of them, find all of their other customers, and invite them to join in. It doesn't matter if it's base code, custom code, or an add-on. The customer has a right to view it if they are licensed for it.

Dirk.Fischer

David Singleton wrote:

Dirk.Fischer wrote:

I'm currently working in a project where the NSC works with some kind of Source Code Removal Tool - It's horror as you are no longer able to debug - I agree with the others that this should never be the way.

Suggest to the customer that they sue the NSC to get access to the source code, since if they were charged time and materials to develop code, they own it. Then change to a partner that is honest.

Also a warning to new Navision customers. Make sure there is a clause in your contract that says the partner MUST give you source code for all work they do, other wise they will be able to control you and you will not be able to change partners.

Unfortionately this is an industry solution and the Source Code Removal only has effect on the 500xxxx-Objects of this NSC, so the customer has no chance to get the functionality needed for their branch from other partners. As there are governmental restrictions and regulations for this branch, it is essential for the customers of this NSC to get continous updates.
But because of complex structures and setups, one single checkbox checked or unchecked could crash the whole billing process, and if a freelance developer or customizing partner of this NSC tries to find out why sth goes wrong it becomes nearly impossible.

David_Singleton

Dirk.Fischer wrote:

Unfortionately this is an industry solution and the Source Code Removal only has effect on the 500xxxx-Objects of this NSC, so the customer has no chance to get the functionality needed for their branch from other partners. As there are governmental restrictions and regulations for this branch, it is essential for the customers of this NSC to get continous updates.

I don't know what the 5,000,000 range is, but it must be some special Add-On range in which case they can get the specific code units locked by Microsoft. And this would be an ISV, NOT the partner. The partner themselves NEVER have reason to lock objects.

Still I would recommend to Navision customers that if their Partner recommends they purchase an Add-On and that Add-On has locked objects, I would reconsider using that Add-On.

Any partner that hacks objects so they can't be read should immediately lose their partner status.

ppavuk

Luc Van Dyck wrote:

Security by obscurity is never a good protection system.

I'm not gonna help you with this one, as I'm against this kind of practices in the NAV channel.

Where is bloody "Like" button!