But surely everybody in MUSCLE understands the need to write fault tolerant
code?

Peter
----- Original Message ----- 
From: "Tommaso Cucinotta" <[EMAIL PROTECTED]>
To: "MUSCLE" <[EMAIL PROTECTED]>
Sent: Friday, May 28, 2004 4:14 PM
Subject: Re: [Muscle] Question MUSCLE authentication


Peter Williams wrote:
> There is simple bit vector, in the public javacard implementation. The
> acl code keys off this vector when performing IBAC.A similar vector
> stores the state of 2nd factor "stong authentication" performed via
> crypto-handshakes, which can be required by the access control decision
> making routines.
>
>  logged_ids = 0x00; // No identities logged in
>
>   /* Logged identities: this is used for faster access    *
>     * control, so we don't have to ping each PIN object    */
>    private short logged_ids;
>

Correct.

> The memory  and access rules for this variable itself may not be managed
> the same way as the underlying PIN object, note. The javacard PIN
> objects can be implemented different ways, for different levels of
> assurance.

This sounds interesting. Do you think in some cases the logged_ids var
may become inconsistent with respect to what the various calls to
PIN.isValidated() would return ? I guess such a problem would arise
only in case of "strange" events such as sudden extraction of the
device, bad voltages/signals on the contacts, ...
The JavaCard platform guarantees atomicity of each APDU exchange
Doesn't it ? (or, what about compliance with such requirement) ?

Bye,
T.

>> From: "joseph schembri " <[EMAIL PROTECTED]>
>> Reply-To: MUSCLE  <[EMAIL PROTECTED]>
>> To: "MUSCLE" <[EMAIL PROTECTED]>
>> Subject: [Muscle] Question MUSCLE authentication
>> Date: Mon, 24 May 2004 16:33:11 GMT
>>
>> Hi !!
>>
>> I have a question about the MUSCLE authentication, I'd like to know
>> how MUSCLE manage the authentication
>> state. I mean, for example, if I verify PIN#0, PIN#1, PIN#2, how
>> MUSCLE keep this information ? Is it in a
>> specific var ?
>>
>> Thanks !
>>
>> Joseph
>>
>> Plus simple, plus fiable, plus rapide : d�couvrez le nouveau Caramail
>> - http://www.caramail.lycos.fr
>>
>> _______________________________________________
>> Muscle mailing list
>> [EMAIL PROTECTED]
>> http://lists.drizzle.com/mailman/listinfo/muscle
>
>
>
> _______________________________________________
> Muscle mailing list
> [EMAIL PROTECTED]
> http://lists.drizzle.com/mailman/listinfo/muscle
_______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.drizzle.com/mailman/listinfo/muscle



_______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to