search

SDkie / seek-for-android

Automatically exported from code.google.com/p/seek-for-android
0 stars 0 forks source link

63xx handling in SCAPI #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Load multiple applets in SIM connected with T=0
2. Run GP GET STATUS command where response is more than one APDU
3. 6310 is returned, SCAPI should take care of protocol handling like with 61xx

What is the expected output? What do you see instead?
expected:
-> 81 F2 20 00 0A 4F 00
   <- 63 10
   -> 01 C0 00 00 00
   <- 6C FF
   -> 01 C0 00 00 FF
<- <FF data> 90 00

actual:
-> 81 F2 20 00 0A 4F 00
<- 63 10

Original issue reported on code.google.com by Daniel.A...@gi-de.com on 17 Feb 2012 at 5:38

GoogleCodeExporter commented 9 years ago 
Attached patch resolved the 6310 issue when baseband is not doing the protocol 
handling

Original comment by Daniel.A...@gi-de.com on 22 Feb 2012 at 11:43

Attachments:

GoogleCodeExporter commented 9 years ago 
Pls verify

Original comment by Daniel.A...@gi-de.com on 8 May 2012 at 2:05

GoogleCodeExporter commented 9 years ago 
Hi, I think this issue also occurs, when selecting an applet with 
openlogicalchannel, where the applet requires a get response by returning 61xx. 
But it responded with 6F00, which is not handling it correctly.

So this patch only fix 63xx sw, but not 61xx.

Can you comment?

Original comment by wongch...@gmail.com on 13 Mar 2013 at 4:57

GoogleCodeExporter commented 9 years ago 
setting old issues from fixed to done

Original comment by Daniel.A...@gi-de.com on 5 Jul 2013 at 2:33