I came across a bug while testing some card services. I only have card
services for one type of card, so I don't know if the bug is in the card
services or not, but looking at how the historical byte length is encoded I
think the bug is in CardID.

An extra byte was being put into the historical bytes due to an offset
calculation problem in the arraycopy call.

The following is the diff output between the original and the fixed
version:

diff -r1.1 -r1.2
108c108
<       System.arraycopy(atr, atr.length - 1 - historicals.length,
---
>       System.arraycopy(atr, atr.length - historicals.length,

Regards,
David Taylor
Forge Information Technology.

http://www.forge.com.au
http://www.protekt.com




---
> Visit the OpenCard web site at http://www.opencard.org/ for more
> information on OpenCard---binaries, source code, documents.
> This list is being archived at http://www.opencard.org/archive/opencard/

! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
! to
!                           [EMAIL PROTECTED]
! containing the word
!                           unsubscribe 
! in the body.

Reply via email to