User's Manual
Table Of Contents
- VX 675
- Contents
- Preface
- Terminal Overview
- Terminal Setup
- Selecting Terminal Location
- Unpacking the Shipping Carton
- Examining Terminal Features
- Examining Connection Ports
- Installing the Paper Roll
- Installing the SIM Card
- Installing the SD Card
- Using the Battery
- Battery Behavior (No Power Pack)
- Connecting the Terminal Power Pack
- Charging the Battery
- Using the VX 675 Base Stations
- Powering Up the Base
- Docking the Terminal on the Base
- Undocking the Terminal from the Base
- Conducting Wireless Transactions
- Conducting Smart Card Transactions
- Using the Magnetic Card Reader
- Connecting to USB Host
- VX 675 ECR (Fiscal Module) Support
- VX 675 3G and GPS Support
- Using the Terminal Keys
- Verix Terminal Manager
- File Authentication
- Performing Downloads
- Downloads and Uploads
- Download Methods
- Download Tools
- Download Content
- Full and Partial Downloads
- Support for Multiple Applications
- Use of I: drive and F: drive
- File Authentication Requirements
- Required Certificates and Signature Files
- The File Authentication Process During an Application Download
- File Group Permissions
- Download an Operating System Update Provided by VeriFone
- File Authentication for Back-to-Back Application Downloads
- Timing Considerations Due to the Authentication Process
- Support for File Compression
- Effect of Downloads on Existing Files and Data
- Direct Operating System Downloads
- Back-to-Back Application Downloads
- Specifications
- Maintenance
- VeriFone Service and Support
- System Messages
- Troubleshooting Guidelines
- Port Pinouts
- ASCII Table
- VX 675 Battery Information
- Glossary
- Application ID
- Application program
- Application prompt
- ASCII
- Back-to-back application download
- Baud
- Bit
- Block
- Boot loader
- Buffer
- Byte
- Calendar/clock chip
- Card reader
- Carrier
- Certificate
- Character
- CONFIG.SYS file
- CPU
- Data
- Data entry
- Data packet
- Default
- Delete
- Diagnostics
- Direct download
- Display
- Download
- File authentication
- Firmware
- Fixed prompt
- Flash memory
- Host computer
- Input
- Interface
- Keyed file character set
- Keyed file editor
- Keyed file record
- Keypad
- Local functions
- Manual transaction
- Memory
- Messages
- Non-volatile memory
- Normal Mode
- Packet
- Packet-switched networks
- Parameter
- Password
- PC
- Peripheral terminal
- Port
- POS terminal
- Power pack
- Prompt
- Protocol
- PTID
- RAM
- Remote host computer
- Scroll
- Search key
- Serial port
- Signature file
- mDRAM
- Subroutine
- Swipe
- Verix Terminal Manager
- Verix Terminal Manager password
- Terminal
- Terminal ID
- Terminal-to-terminal application upload
- Track 1, 2, or 3 data
- Transaction
- Variable
- Volatile memory
- Index
- Contact VeriFone
FILE AUTHENTICATION
Introduction to File Authentication
VX 675 R
EFERENCE GUIDE 87
Deployment Terminals
While the application development process is being completed and while the new
application is being tested on a development terminal, a sponsor can order
specific sponsor and signer certificates from the VeriFone CA to use to logically
secure sponsor and signer privileges when the VX 675 terminal is prepared for
deployment.
Customer-specific sponsor and signer certificates are usually downloaded to a VX
675 terminal as part of the standard application download procedure performed
by a deployment service. In this operation, the new sponsor and signer certificates
replace the development sponsor certificate that is part of the factory set of
certificates, as shown in Figure 27.
When the sponsor and signer certificates are downloaded and successfully
authenticated, the terminal is ready to deploy.
Ultimately, it is the sponsor’s decision how to implement the logical security
provided by file authentication on a field-deployed terminal. Additional certificates
can be obtained from the VeriFone CA anytime to implement new sponsor and
signer relationships in deployment terminals. VeriShield Retain allows for multiple
sponsors and signing certificates in a terminal. This allows the flexibility of unique
signatures for each executable or data files.