User's Manual

FILE AUTHENTICATION
Introduction to File Authentication
VX 675 R
EFERENCE GUIDE 89
Table 9 Differences Between Required Inputs
Development Terminals Deployment Terminals
Manufacturing inputs to the file signing
process are included, together with the
VeriShield File Signing Tool in the VX 675
SDK. These inputs make it possible for
anyone who has the
VX 675 SDK to sign and authenticate
files.
The required inputs to VeriShield File
Signing Tool must be obtained from the
VeriFone CA to logically secure the
sponsor and signer privileges for the
terminal.
The following three unique inputs, which
are issued at customer request by the
VeriFone CA, are required for the file
signing process, as well as the application
files you want to sign and authenticate:
• Developer signer certificate: This
unique certificate is a required input for
VeriShield File Signing Tool and must
be downloaded to the terminal along
with the signature files and target
application files to authenticate, unless
already downloaded to the terminal in a
previous operation.
• Developer signer private key: The
VeriFone CA issues this unique,
encrypted private key file (*.key) to an
authorized signer at the sponsor’s
request. The signer private key is a
required input to VeriShield File Signing
Tool, but does not have to be
downloaded to the terminal.
• Developer signer PIN: The VeriFone
CA issues this unique password to an
authorized signer at the sponsor’s
request. The customer signer password
is a required input to VeriShield File
Signing Tool, but it does not have to be
downloaded to the terminal.
Note: The customer sponsor certificate,
which authenticates the
customer signer certificate, is
usually downloaded to the
terminal with the customer signer
certificate, but it is not a required
VeriShield File Signing Tool input
when signing files.