LKJC

Seu parceiro de soluções de automação

11 de fevereiro de 2018

PROTEÇÃO DE CÓDIGO FONTE NO STUDIO 5000 LOGIX

DESIGNER
Ao trabalhar com um cliente em um projeto recente do RSLogix 5000 (agora chamado
Studio 5000), houve a necessidade de proteger alguns códigos-fonte
proprietários. Nesse caso específico, desenvolvemos uma instrução add-on (AOI)
customizada para ser usada dentro do projeto que continha alguma lógica exclusiva
que o cliente desejava proteger. Isso é incrivelmente fácil de fazer. A Rockwell fornece
uma ferramenta fácil para isso que vem pré-embalada com o RSLogix. 

Como proteger a propriedade intelectual ou algoritmos delicados ao abrir parte do

código para modificação ou solução de problemas é bastante comum, pensei em
compartilhar algumas das informações que encontrei e fornecer algumas etapas
fáceis para bloquear seu código. A propósito, enquanto eu o oriento na configuração
de uma AOI para proteção de origem, você também pode usar a mesma abordagem
para proteger as rotinas.

Observe que todas as informações abaixo podem ser encontradas em vários

formulários em dois documentos úteis publicados pela Rockwell Automation que eu
recomendo que você baixe para referência:

 Instruções add-on dos controladores Logix5000

 Segurança dos controladores Logix5000
 Nota técnica 22601
Habilitando a proteção da fonte
Fora da caixa, a proteção do código-fonte não está habilitada no RSLogix 5000.
Portanto, se você nunca o usou, há boas chances de que nunca tenha sido
ativado. Para verificar, abra o projeto em que está trabalhando e procure em
Ferramentas >> Segurança. Se você não vir uma opção para "Configurar proteção de
origem", será necessário ativá-la.

Eu presumiria que você realmente só precisa fazer uma mudança rápida no registro,
mas é ainda mais fácil do que isso, pois a Rockwell fornece uma ferramenta gratuita
que você pode baixar e executar para cuidar disso para você. Allen Bradley fornece
algumas boas instruções para o processo que descreve os diferentes métodos para
diferentes rotações do RSLogix na segurança dos controladores Logix5000 . No meu
caso, usando a rev 20, precisei baixar a ferramenta de proteção de fonte de Allen
Bradley. Para encontrá-lo, comecei na página de download do software e pesquisei
Downloads do RSLogix. Você deve vê-lo listado como "Ferramenta de proteção de
fonte RSLogix 5000". Este é um download rápido. Após a execução, reinicie o RSLogix e
você deverá ver uma nova opção em Ferramentas >> Segurança: Configurar proteção
da fonte.
Ok, after enabling, you can choose your newly available option and you will now be
prompted to specify a Source Key File location. Go ahead and choose a location. If you
don't have a source key file in the specified directory, you will be asked if you would
like to create one. This source key file will contain your keys for any protection you
establish. This file can be moved from computer to computer, or it can be built locally
by adding the keys you create. Go ahead and create a new one; once you've done so,
you're ready to lock down your code.

Protecting an AOI
For a quick demo, I created a new project with a single Routine called 'MyRoutine' and
a single AOI, 'MyAddOnInstruction.' Once you open up Source Protection Configuration
from Tools >> Security, you will see that your programs and Add-On Instructions will
be available. You can configure different keys and settings for each program and AOI,
but lets just walk through configuration of 'MyAddOnInstruction.' Take a look and
notice that there are currently no Source Keys defined.
Select your AOI you would like to protect and choose "Protect." A Source Key dialog will
open allowing you to select or create a source key to apply to your selected
component (in this case, our AOI). I'm going to create a new one, "MyKey" and name it
LKJC. If you choose not to show the key (characters will not be shown on the screen)
you will need to confirm the key a second time. I prefer to just see what I'm typing. You
can also define a Source Key Name. This is really just a friendly name to associate with
your key (think of user name::password, key name::key) that will be shown in the
Source Protection Dialog to protect your key from prying eyes.
The checkbox in this dialog is worth discussing in a little more detail. You have two
choices for the level of protection you are enabling. Leaving this checkbox unchecked
will completely lock and hide the code source code from anyone without the key. Any
one viewing the project (or any project containing this AOI) without the key will not be
able to view, access, or edit the source code for the instruction. Selecting the checkbox
will allow a user to view, but not to modify the source code, in effect making it read
only. Of course with either selection, if you have the key, you have full access.

It should be noted that in addition to protecting any sensitive code, this can also be
used as a method of source or version control and can be a great way to prevent
unauthorized or unintended edits to sections of source code that have been validated
or released.

Getting back to our walkthrough, let's go ahead and leave the checkbox unchecked
and select OK. This will bring us back to the Source Protection Configuration dialog
again, but you will now see that the key "LKJC" has been added to our AOI and it is not
selected as viewable for anyone without the key.

We're done here. Choose "Close" to exit the dialog and take a look at your project tree.
You shouldn't notice any changes. You can still expand and see both Tags and Logic for
the AOI we just protected. However, to see what it looks like to someone without the
key, I'm going to save the project, exit RSLogix, and delete my key file. Now, after
reopening the project we can see that I am not able to expand the AOI - there is no
access to the Tags or Logic for the instruction.

If we dig a little deeper and open up the Source Protection Configuration dialog again,
we will see that 'MyAddOnInstruction' is protected and has an unknown source key.
Selecting the AOI and choosing "Protect" will bring us back to the Apply Source Key
dialog. Attempting to apply a new source key other than the one we already created
for this instruction will give an error and will not allow us to unlock it. However, I luckily
grabbed a screenshot of the earlier showing me that I used the key 'MyKey.' Sure
enough, entering this key will unlock the AOI and allow access to the source code
again.

It is also worth taking the time here to export our AOI. Normally, an exported AOI will
be saved in human readable text in an XML type format (try it!). However, when source
protection has been enabled, this exported file is encrypted.

Before I wrap this up, I want to get back to one more point. I touched upon this earlier,
but its worth mentioning that there are many reasons one may want to use Source
Protection within their project. In addition to protecting proprietary code, it can also be
a useful method of source control. A good example may be a custom motor
implementation in a large project. Once development and testing has been completed
on the instruction or routine, the code could be locked by the creator to prevent any
accidental changes by others. By locking and then exporting to a library, other
developers can then use the instruction and be guaranteed that the source code has
not been modified.

This, combined with the version information available for each AOI and routine, can be
a great way to manage a shared library of reusable code. We strives to make code as
reusable as possible as a means to decrease development time (and cost), increase
reliability, and provide for scalability and modularity. Combining this with versioning
control provides for an easy way to maintain a library for all our engineers to share.

Finally, a quick disclaimer about security. This solution will probably serve for the
majority of purposes, however in the case of extremely valuable intellectual property, I
would always strongly recommend consulting with experts before trusting that this is
bullet proof.

In case you have lost the KEY... Read This.

Share

COMMENTS
POPULAR POSTS
12 de fevereiro de 2018

COMO DESCRIPTOGRAFAR / DESBLOQUEAR A PROTEÇÃO DA

FONTE RSLOGIX 5000
Compartilhar

 2 comentários

4 de fevereiro de 2018

STUDIO 5000 / RSLOGIX 5000: ERRO FATAL 0XC0000005 NO

WINDOWS 8 / 8.1 / 10
Compartilhar

 6 comentários

Desenvolvido por Blogger

Imagens temáticas por sololos

Seguir por E-mail

 

lkjcontrols
 VISITE O PERFIL

Etiquetas
Arquivo