VeriFone VX 520 Specifications Page 89

  • Download
  • Add to my manuals
  • Print
  • Page
    / 190
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 88
FILE AUTHENTICATION
Introduction to File Authentication
VX 520 R
EFERENCE GUIDE 89
Table 13 Differences Between Required Inputs
Development Terminals Deployment Terminals
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:
Signer certificate, with the filename
VxSIGN.CRT
Signer private key, with the filename
VXSIGN.KEY
Developer signer certificate: This
unique certificate is a required input for
the 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 the 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 the 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.
Page view 88
1 2 ... 84 85 86 87 88 89 90 91 92 93 94 ... 189 190

Comments to this Manuals

No comments