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
VeriShield File Signing Tool
VX 675 R
EFERENCE GUIDE 97
Please note also how the command-line mode switches described in Table 11 are
used in this example:
filesign -L -f file.out -s file.p7s -c vxsign.crt -k vxsign.key
• The -L switch indicates to store the application file in the flash file system
instead of the target group’s (default) I: drive file system. (The target group for
the download must be selected from Verix Terminal Manager when the
download is performed.)
• The -f switch indicates that the application file “file.out” must be signed
by the file signing tool.
Executable files, such as *.out and *.lib files, must always be signed if
they are to run on the terminal following a download. Depending on the
-S, -s Name of the signature file
(*.p7s) for VeriShield File
Signing Tool 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 drive F: file
system.
If you do not use this switch to
specify F: drive as the target file
destination, it is stored by default
in the I: drive.
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: Signature files must be
downloaded into the
target file group’s I:
drive.
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 F: drive, its *.p7s file is
moved into the F: drive system. If,
however, you set the *FA variable
in the file group’s CONFIG.SYS
file to 0, all signature files are
deleted from memory when file
authentication is complete.
Removing *.p7s files will prevent
application files from executing
after a back-to-back download.
a. The switches described are not case-sensitive and can be entered on the command line in
any order.
Table 11 Command-Line Mode Switches for VeriShield File Signing
Tool
a
Switch Description Requirements