This content has been marked as final. Show 2 replies
Deciding to reset is a task for the reader and its application, not the card.
Under ISO/IEC 7816-3 (T=0 or T=1), the card can not just decide to reset without breaking the protocol. The best it could do under T=0 is stay mute until the reader decides to reset it (which the reader can decide to do in either of two ways: cold or warm).
Ah, and I know no standard API for staying mute under Java Card. An infinite loop in an applet will typically NOT make the card mute.