Extended APDU support
2015-06-28 15:09
253 查看
http://pcsclite.alioth.debian.org/ccid_extended_apdu.html
To be able to use an extended APDU you need to have:
A T=1 card
A smart card reader working in TPDU or Extended APDU
A smart card reader can work using 4 different exchange levels:
Character
TPDU
Short APDU
Short and extended APDU
The exchange level of a reader is contained in the dwFeatures field of the CCID descriptor.
You can get this information using the parse command included in the driver source code.
Character level: Only very few readers work using this method. I don't know if/how they support extended APDU.
TPDU level: With this exchange level a lot of the work is done in the driver. In particular support of extended APDU is managed by the driver and the CCID driver implements it.
Short APDU: These readers are easy to use at a driver point of view but are then limited to short APDU only. Support of extended APDU is then not possible.
Some readers claim they support short APDU only but can use extended APDU when used with the manufacturer Windows driver. Maybe the Windows driver switches the reader in TPDU mode or something similar. That is not a documented CCID feature and so is not used in my CCID driver. If you can get information on this from the reader manufacturer I may include support of extended APDU for the reader in my driver.
Short and extended APDU: Support of extended APDU is offered by the reader.
you can send Extended APDU in T=0 as well but for that your card must be supported "javacardx.apdu". Please refer javadoc link
Here is method to know what is supported by your card.
You will get all the package AID in response of this command then search for AID
"A0000000620209".
if available then javacardx.apdu is supported.
For more info abt "Get status" command please refer GP 2.2.1
An extended APDU is an APDU (command) with data and/or response of more than 256 bytes and up to 65536 bytes. See ISO 7816-4 for more details.
The CCID driver supports extended APDU. But this support may be limited by the smart card reader itself.
To be able to use an extended APDU you need to have:
A T=1 card
A smart card reader working in TPDU or Extended APDU
A smart card reader can work using 4 different exchange levels:
Character
TPDU
Short APDU
Short and extended APDU
The exchange level of a reader is contained in the dwFeatures field of the CCID descriptor.
You can get this information using the parse command included in the driver source code.
Character level: Only very few readers work using this method. I don't know if/how they support extended APDU.
TPDU level: With this exchange level a lot of the work is done in the driver. In particular support of extended APDU is managed by the driver and the CCID driver implements it.
Short APDU: These readers are easy to use at a driver point of view but are then limited to short APDU only. Support of extended APDU is then not possible.
Some readers claim they support short APDU only but can use extended APDU when used with the manufacturer Windows driver. Maybe the Windows driver switches the reader in TPDU mode or something similar. That is not a documented CCID feature and so is not used in my CCID driver. If you can get information on this from the reader manufacturer I may include support of extended APDU for the reader in my driver.
Short and extended APDU: Support of extended APDU is offered by the reader.
you can send Extended APDU in T=0 as well but for that your card must be supported "javacardx.apdu". Please refer javadoc link
Here is method to know what is supported by your card.
00 A4 04 00 <length of Card manager AID> <AID> [Select card manager]
00 20 00 00 08 <Card manager PIN> [verify card manager PIN]
00 80 F2 20 00 02 4F 00 - [get status command with P1 20] and [Executable Load Files and Executable Modules 4F00]
You will get all the package AID in response of this command then search for AID
"A0000000620209".
if available then javacardx.apdu is supported.
For more info abt "Get status" command please refer GP 2.2.1
An extended APDU is an APDU (command) with data and/or response of more than 256 bytes and up to 65536 bytes. See ISO 7816-4 for more details.
The CCID driver supports extended APDU. But this support may be limited by the smart card reader itself.
相关文章推荐
- 佛说长寿灭罪经译文
- Python实现将绝对URL替换成相对URL的方法
- OJ期末模考I
- 135.删除字符串中字符ASCII为奇数的数。
- [Q]pdfFactory虚拟打印机的安装
- python __str__ & __repr__ & __cmp__
- FTP服务器搭建
- Senergy.Interactive.Petrophysics.v4.2.2013.275 1CD(交互式测井分析工具)
- google chrome can not be run as root
- 使用TextRank算法为文本生成关键字和摘要
- ARM编程工具篇——交叉编译
- 入职互联网公司一个月
- VS配置路径和宏
- Redis 笔记与总结6 Redis 高级应用之 事务处理、持久化操作、pub_sub、虚拟内存
- 话说云服务器是降价,还是彻底免费?
- Schlumberger Oil Field Manager(OFM) 2012.1-ISO 1CD(油田日常监控和管理软件包)
- 深度学习系列之CNN核心内容
- asp.net 安装数据库,以及修改web.config文件
- OJ期末模考H
- 机房收费系统——组合查询