OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: [Muscle] new MSCGetStatus approach - e.g. for getting retry counter of PINs

From: Karsten Ohme (widerstandt-online.de)
Date: Sun Oct 23 2005 - 07:14:42 CDT


Hello,

Klaus Peter Gungl wrote:
>
> Hello,
>
> for the choice of function call I recommend to consider APDU and ISO
> naming. As GET STATUS is a defined APDU command for Global Platform
> cards, this could be confusing if you select a very similar naming that
> should apply to PIN and retry counter.
> But then again... naming is always a difficult choice to make...

This function already exists with this name in MuscleCard API 1.3 and in
the APDU specification for the applet, if another name is crucial, e.g.
GET STATE, then this function can be renamed. Some naming suggestions?
Up till now this function returns the free memory, available memory,
protocol version, software version, logged IDs and used keys. If
somebody is programming with the MuscleCard API he can distinguish
between the meaning of one and the other.

> Best regards,
> Klaus.

Best regards,
Karsten

>
> *Karsten Ohme <widerstandt-online.de>*
> Sent by: muscle-bounceslists.musclecard.com
>
> 22.10.2005 20:37
> Please respond to
> MUSCLE
>
>
>
> To
> MUSCLE <musclelists.musclecard.com>
> cc
>
> Subject
> [Muscle] new MSCGetStatus approach - e.g. for getting retry counter
> of PINs
>
>
>
>
>
>
>
>
> Hello,
>
> I would propose a redefined function MSCGetStatus().
> The MSCGetCapabilities approach can be used. So any information needed
> can be specified with a tag and also proprietary tags can be used and
> handled by the plug in or the token (applet).
> There are some defined tags, e.g. protocol version, free memory, ... the
> information currently contained in the struct MSCStatusInfo,
>
> For the retry counter of the pins or keys this tag can be a short
> beginning with a byte xy and after this a
> number for which pin the status should be retrieved (including a m.s.
> bit which must be set if this information should be returned for the
> corresponding unblock pin). Also some identifying information like a
> serial number of the token can be queried with this.
>
> Karsten
> _______________________________________________
> Muscle mailing list
> Musclelists.musclecard.com
> http://lists.drizzle.com/mailman/listinfo/muscle
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Muscle mailing list
> Musclelists.musclecard.com
> http://lists.drizzle.com/mailman/listinfo/muscle

_______________________________________________
Muscle mailing list
Musclelists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle