Re: [opensc-devel] questions on {ERASE, WRITE, UPDATE} BINARY commands

2012-06-08 Thread Andreas Schwier (ML)
Hi Peter, ERASE and WRITE are left-overs from the old smart card days. Most - if not all - cards and applications today only implement UPDATE BINARY. There is also no common understanding that UPDATE BINARY must not extend the length of an EF. Some implementations maintain a maximum EF and a

[opensc-devel] is this card? is it supported?

2012-06-08 Thread helpcrypto helpcrypto
Hi! Our company -finally-, is going to change the smartcard we are using. Actually we have a non-cryptographic, and seems we are sitching to 3B 6F 00 00 80 66 B0 07 01 01 77 07 53 02 31 24 82 90 00 Looking at http://ludovic.rousseau.free.fr/softwares/pcsc-tools/smartcard_list.txt i have found

Re: [opensc-devel] questions on {ERASE, WRITE, UPDATE} BINARY commands

2012-06-08 Thread Peter Marschall
Hi Andreas, thanks a ton. That explains it very well and answers all my questions. On Friday, 8. June 2012, Andreas Schwier (ML) wrote: Hi Peter, ERASE and WRITE are left-overs from the old smart card days. Most - if not all - cards and applications today only implement UPDATE BINARY.

Re: [opensc-devel] is this card? is it supported?

2012-06-08 Thread Ludovic Rousseau
2012/6/8 helpcrypto helpcrypto helpcry...@gmail.com: Hi! Hello, Our company -finally-, is going to change the smartcard we are using. Actually we have a non-cryptographic, and seems we are sitching to 3B 6F 00 00 80 66 B0 07 01 01 77 07 53 02 31 24 82 90 00 Looking at