Rockwell Automation Logix5000 Controllers Security Programming Manual - Manual (Page 37)

Configuring source protection in the Logix Designer application Chapter 4
5. Click OK.
The Source Protection Configuration dialog box reappears.
For version 19 and later of the application, source keys may have names. If
the source key has a name, the name appears instead of the source key. In
this example, the name Field Engineer is displayed instead of the source key.
Important: Source key names cannot be added to existing source keys through the
Logix Designer application.
See
Source key file on page 37 to learn how to associate a name to an
existing source key.
For version 19 and later of the application, unnamed source keys are
obfuscated. Three black circles appear after the last character or any
character beyond the fifth character to provide security.
6. Close the Source Protection Configuration dialog box and save the
project file.
Source key file
Source keys that are available to the application through an sk.dat file are
unencrypted. We recommend that you write down the source keys or back up and
store the sk.dat file in a secure location. If necessary, the individual keys can be
distributed or provided to the necessary parties.
Important: Source key files are created in an ANSI format in RSLogix 5000 version 18 and earlier. RSLogix
5000 version 19 and later, and Logix Designer creates UTF-8 formatted sk.dat files. ANSI sk.dat
files modified in RSLogix 5000 version 19 and later, are converted to UTF-8 sk.dat files.
Source keys must not appear on the first line of a UTF-8 formatted sk.dat file. The first line of
UTF-8 formatted sk.dat files is ignored by RSLogix 5000 software version 18 and earlier.
Versions 19 and later insert a header on the first line of the sk.dat file if one is not already
present.
Rockwell Automation Publication 1756-PM016G-EN-P - October 2014 37