User's Manual

FILE AUTHENTICATION
File Authentication and the File System
VX 675 R
EFERENCE GUIDE 93
If the signature file authenticates its target file, and if the *FA variable is present in
the
CONFIG.SYS file of the target file group and is set to 1, the signature file is
retained in memory and is automatically moved, if necessary, into the same
logical file system (I: or F:) as the target file it authenticates. That is, if the target
file is identified as an F: drive file, the signature file is also identified as an F: drive
file; if the target file is identified as an I: drive file, the signature file is also is
identified as an I: drive file.
If the signature file authenticates its target file and the *FA variable is present in
the
CONFIG.SYS file of the target file group and is set to 0, the signature file is
erased when its target file is authenticated.
If you intend to perform back-to-back downloads, as described in Chapter 6, all
signature files must be retained in the VX 680 terminal’s application memory,
together with the target application files they authenticate.
Restrictions on Downloading Different File Types
A typical application download includes a variety of different file types. The
following restrictions in Table 10 describe how you can download different kinds of
files to the VX 680 terminal and how files are stored in the file system:
NOTE
Normally signature files are retained in the terminal even after being used to
authenticate executable (code) or data files. This is to facilitate back-to-back
downloads, as described in Chapter 6. Users who do not intend to perform
back-to-back downloads can remove signature files after use, gaining space for
other files. Automatic removal is performed if the user sets *FA=0 in the
CONFIG.SYS file of Group 1. The main reason for using *FA is to force automatic
removal. If the user desires the default behavior (retain signature files, to allow
for back-to-back downloads), the user does not need to set *FA.
NOTE
To control if signature files are retained or deleted when they are processed by
the file authentication module, you must use the protected
CONFIG.SYS variable
*FA as documented in the Verix eVo Volume I: Operating System Programmers
Manual (VPN DOC00301).
Table 10 Download File Extensions
File Type Restriction
Certificate
(*.crt)
Must be downloaded into the I: drive of the target file group
(GID1 – GID15) selected in Verix Terminal Manager.
Signature
(*.p7s)
Must be downloaded into the I: drive of the target file group
(GID1 – GID15) selected in Verix Terminal Manager.
Operating system Must be downloaded into Group 1 I: drive. When the OS files,
related certificates and signature files are authenticated, they are
automatically moved from Group 1 I: drive into the Group 0 sub-
partition reserved for the operating system.