Specifications

FILE AUTHENTICATION
FILESIGN.EXE File Signing Tool
O
MNI 37XX REFERENCE MANUAL 75
Command-Line
Entries for
FILESIGN.EXE
Table 18 lists and describes the switches that make up the command-line mode
syntax for FILESIGN.EXE.
Command-Line
Mode Syntax
Example
In the FILESIGN.EXE command-line entry example below, please note that the
syntax used applies to an Omni 37xx development terminal with the factory set of
certificates, and not to a deployment terminal. There are two differences:
Table 18 Command-Line Mode Switches for FILESIGN.EXE
Switch Description Requirements
-C, -c Signer certificate file name (*.crt). Required input for development terminals and
deployment terminals.
For development terminals, you can use the
default signer certificate, K2SIGN.CRT.
For deployment terminals, you must use the
signer certificate issued by the VeriFone CA.
-K, -k Signer private key filename (*.key). Required input for development terminals and
deployment terminals.
For development terminals, you can use the
default signer private key, K2SIGN.KEY.
For deployment terminals, you must use the
signer private key provided by the VeriFone CA.
-P, -p Signer password for decrypting the signer
private key.
Required input only for deployment terminals.
The VeriFone CA issues and securely conveys
this password to an authorized signer.
-F, -f Name of the application file to sign (*.out,
*.lib, or other file type).
Required for development terminals and for
deployment terminals.
-S, -s Name of the signature file (*.p7s) for
FILESIGN.EXE to generate for the target
application file.
Required for development terminals and for
deployment terminals.
-L, -l Specifies to store the target application file
to sign and authenticate in the flash (drive
F:) file system.
If you do not use this switch to specify flash
as the target file destination, it is stored by
default in the RAM file system (drive I:).
Optional entry.
This switch assigns an F: prefix to the name of the
*.out or *.lib file to download, and also stores this
information in the signature file as part of the
special filetype attribute.
Note: NOTE: Signature files must be
downloaded into the target file group’s
RAM.
If the target file is authenticated, the
corresponding *.p7s file is moved to the same
memory area as the target file it authenticates.
For example, if the target file is stored in flash
(F:), its *.p7s file is moved into the flash file
system. If, however, you set the *FA variable in
the file group’s CONFIG.SYS file to 0, all
signature files are deleted from RAM when file
authentication is complete.