[Muscle] debugging muscle?

[David Corcoran]

Iain,

Correct - the MuscleCard support for OpenSC actually places a PKCS#15  
structure on the MuscleCard applet's filesystem (single level)
libmusclecard, the plugins, and the PKCS#11 module for MuscleCard  
could then be phased out over time - placing the multi-card support  
under
the OpenSC PKCS#11 module.

This makes the most sense since the Muscle framework, applet, etc was  
designed for JavaCards only and OpenSC is a bit more generic.

Thanks,
Dave



On Nov 26, 2006, at 5:42 PM, Iain MacDonnell wrote:

>
>
> Andreas Jellinghaus wrote on 11/26/06 02:12 PM:
>> Iain MacDonnell wrote:
>>> The "muscletest" tool that is built with libmusclecard (but not
>>> installed anywhere by default - find it in src/.libs) will
>>> list objects,
>> thanks, will have a look.
>>> but I'm not sure how the PKCS#15 files for OpenSC
>>> get implemented as MuscleCard objects... is there a 1:1 mapping?
>> directories get the object id of the dir name, files the object
>> id of the dir+file name. so it somehow emulates a real filesystem.
>>> muscleTool should be able to list objects too...
>>> http://muscleapps.alioth.debian.org/
>> ok, thanks.
>>> Those are plugins for libmusclecard - if libmusclepkcs11 is  
>>> obsolete,
>>> then libmusclecard may be too (if there's no PKCS#11 interface,  
>>> it's not
>>> of much value, IMO).
>> no, the idea is to merge opensc and muscle, to have one library
>> that can speak to all smart cards. applications can use
>> opensc-pkcs11 then. I think it is better to have one firefox and
>> ssh and pam module that can use opensc-pkcs11 that works with many
>> cards, then to have specialised software for some cards only.
>
> My point is that if we're going to use OpenSC, libmusclecard (and
> associated plugins) are no longer of any value. OpenSC's support for
> MuscleCards doesn't use libmusclecard (AFAIK?).
>
>
>> easier for users and distributions at least I think.
>>> CFlexPlugin is (was?) for *Crypto*Flex, not CyberFlex.
>> ah, thanks. I didn't know you could put plugins on cryptoflex
>> cards at all. (it is meant to be loaded on the card, right?)
>
> No, the plugins don't go on the card - they are to libmusclecard what
> "card drivers" are to OpenSC - MCardPlugin knows how to talk to
> JavaCards with the MuscleCard plugin, CFlexPlugin knows how to talk to
> CryptoFlex cards and AuthICPlugin knows how to talk to Oberthur
> AuthentIC cards.
>
>     ~Iain
>
>
>
>
>
> _______________________________________________
> Muscle mailing list
> Muscle at lists.musclecard.com
> http://lists.drizzle.com/mailman/listinfo/muscle
>

------------------------------------------------------------------------ 
------------
David Corcoran        corcoran at identityalliance dot com
   Identity Alliance        http://www.identityalliance.com
   phone: 260-399-1648   fax: 260-488-2455

   Smart Cards, Biometrics, Training, Identity Management
------------------------------------------------------------------------ 
-------------