Red Hat CERTIFICATE SYSTEM 8.0 - MANAGING SMART CARDS WITH THE ENTERPRISE SECURITY CLIENT 1-23-2010 Manual page 44

Managing smart cards with the enterprise security client
Table of Contents

Advertisement

Chapter 3. Using the Enterprise Security Client
• The Enterprise Security Client loses the connection to the smart card. This can happen when
problems occur communicating with the PCSC daemon.
• The connection between the Enterprise Security Client and TPS is lost.
Smart cards can report certain error codes to the TPS; these are recorded in the TPS's tps-
debug.log or tps-error.log files, depending on the cause for the message.
Return Code
General Error Codes
6400
6700
6982
6985
6a86
6d00
6e00
Install Load Errors
6581
6a80
6a84
6a88
Delete Errors
6200
6581
6985
6a88
6a82
6a80
Get Data Errors
6a88
Get Status Errors
6310
6a88
6a80
Load Errors
6581
6a84
6a86
6985
Table 3.1. Smart Card Error Codes
36
Description
No specific diagnosis
Wrong length in Lc
Security status not satisfied
Conditions of use not satisfied
Incorrect P1 P2
Invalid instruction
Invalid class
Memory Failure
Incorrect parameters in data field
Not enough memory space
Referenced data not found
Application has been logically deleted
Memory failure
Referenced data cannot be deleted
Referenced data not found
Application not found
Incorrect values in command data
Referenced data not found
More data available
Referenced data not found
Incorrect values in command data
Memory failure
Not enough memory space
Incorrect P1/P2
Conditions of use not satisfied

Advertisement

Table of Contents
loading

Table of Contents