Specifications

FILE AUTHENTICATION
Introduction to File Authentication
58 OMNI 37XX REFERENCE MANUAL
3 The application file becomes a required input for the FILESIGN.EXE tool
(included in the SDK).
4 The default certificate (K2SIGN.CRT) and default key (K2SIGN.KEY) included
in the SDK are inputs for the FILESIGN.EXE tool.
5 Using the application file, default certificate, and default key, FILESIGN.EXE
creates a signature file (*.p7s).
6 The signature file and the original application file are loaded into a
development terminal, where the following actions occur:
a The terminal’s operating system searches for signature files.
b When a signature file is found, the operating system then searches for a
matching application file.
c When a matching application file is found, the operating system compares
the signature file’s signature against the values stored in the application
file’s calculated signature.
d If these values match, the two files are authenticated, and the
ATTR_NOT_AUTH bit is set to 0.
7 The application file is tested and debugged.
8 After the application file is fully debugged, it becomes an input for the
deployment process.
Figure 14 illustrates the development process.