Specifications

PERFORMING DOWNLOADS
Omni 37xx Download Differences
92 OMNI 37XX REFERENCE MANUAL
1 All certificate files (*.crt), signature files (*.p7s), and application files (*.out,
*.lib, *.fon, *.vft, *.dat, and so on) download to the Omni 37xx deployment
terminal in batch mode.
2 When the terminal restarts after the download, the file authentication module
searches the RAM-based file system for the following two file types:
• Authenticated certificate files (*.crt) to add to the permanent certificate tree
• Signature files (*.p7s) that authenticate corresponding target application
files
Certificate files and signature files can download into the RAM of any file
group. For this reason, the file authentication module searches through the
entire file system (all file groups) for new files with these filename extensions
each time the terminal restarts.
3 The file authentication module builds a list of all newly detected certificates
and signature files. If no new certificates or signature files are located, the
module just returns. If one or more new files of this kind are detected, the file
authentication module starts processing them based on the list.
4 Certificates are always processed first (before signature files). The processing
routine is called one time for each certificate in the list. If a certificate is
authentic, it is noted, and the next certificate processed. This process
continues in random order until all certificates are authenticated.
When a certificate file in the processing list is authenticated, the
“Authenticated” message displays below the corresponding filename. If it fails
to be authenticated, the “Failed” message displays for five seconds and the
terminal beeps three times (see Figure 21). The routine then resumes
processing and continues until all certificates are successfully processed.
The processing routine gives you both visible and audible indications if a
specific certificate successfully authenticates. The file authentication module
does not halt the process if a certificate fails to authenticate, but continues to
the next step: authenticating signature files.
If one or more certificates fail to authenticate, the ensuing file authentication
process based on signature files probably also fails, with the result that an
application is not authenticated and is not allowed to execute on the terminal.
When a certificate file is authenticated, the data it contains is added to the
certificate tree and the certificate file is deleted from the RAM. When all
required certificates are authenticated and stored in the certificate tree, the file
authentication process for signature files can proceed.