[Fwd: RE: [Muscle] APDUs]

[Jeff Fern]

Peter,

Thanks for your reply ... I am on a very steep learning curve with all
this stuff. The Omnikey dev. guide says:

"Please refer to the [PCSC 2.01] and [MIFARE] for documentation of PC/SC
2.0 compliant Mifare card access. The following section only describes
usage of functions that are not already documented in [PCSC 2.01]. They
are part of an OMNIKEY proprietary extension of PC/SC."

The only info within the doc is regarding increment & decrement counter
and MAD access.

I understand the access requirements for each read/write command, and
using the sample windows application have got that working ... I was
hoping that wherever I find the APDUs for read/write would also have the
access command APDUs.

Regards,
-Jeff Fern


> Jeff,
>
> As far as I can tell PC/SC does not support memory cards. But some card
> reader suppliers implement proprietary APDU-format commands on their
> system interfaces, commands that their card readers convert into Mifare
> commands - that will be what Scott is pointing you to.
>
> Also are you aware that you need to use access keys for all read and
> write operations with a Mifare card?
>
> Regards,
>
> Peter
>
> Peter Tomlinson
> Iosis Associates
> Bristol UK
> www.iosis.org.uk
> www.pssg.biz
>
> -------- Original Message --------
> Subject:     RE: [Muscle] APDUs
> Date:     Sat, 7 Jul 2007 21:26:42 +0100 (BST)
> From:     Jeff Fern <musclecard at fcse.co.uk>
> Reply-To:     MUSCLE <muscle at lists.musclecard.com>
> To:     MUSCLE <muscle at lists.musclecard.com>
> References:     <468E7AE0.3010306 at fcse.co.uk>
> <A4628A7C27BF0D48847FD4AB8536731D96AD0F at blinky.mobile-mind.com>
>
>
>
> Scott,
>
> Thanks for your reply. I think that it's the card I want to talk to - I
> want to be able to read and write to the blocks on it.
>
> I have looked at that document, it basically says for MiFare most of the
> PCSC commands work, there are a couple of custom ones which are listed.
> The issue I'm having is I can't find the PCSC commands (or document which
> lists them).
>
> Regards,
> -Jeff Fern
>
>>  Jeff:
>>
>>  Are you stumped by commands for the card or the card reader? The
>>  develper's manual for CardMan is at
>>
>>
> omnikey.aaitg.com/fileadmin/CardMan__5x21-CL_Reader_Developers_Guide_v1_11.pdf
>>
>>
>>  It has some MiFare information.
>>
>>  Cheers, Scott
>>
>>  -----Original Message----- From: muscle-bounces at lists.musclecard.com
>>  on behalf of Jeff Fern Sent: Fri 7/6/2007 1:24 PM To:
>>  muscle at lists.musclecard.com Cc: Subject: [Muscle] APDUs
>>
>>
>>
>>  Hi All,
>>
>>  I've just got JPC/SC working with my Cardman 5321 and a MiFare 1k
>>  card. The windows software that came with the card reader includes
>>  something that allows you to authenticate, read and write etc. to the
>>  card however all I can see to do with JPC/SC is send APDU commands to
>>  the card - the issue is apart from reading the UID I haven't been
>>  able to find any specs for what APDUs to send. Can anyone point me in
>>  the right direction?
>>
>>  Many thanks, -Jeff
>>
>>  -- This message has been scanned for viruses and dangerous content by
>>  MailScanner, and is believed to be clean.
>>
>>  _______________________________________________ Muscle mailing list
>>  Muscle at lists.musclecard.com
>>  http://lists.drizzle.com/mailman/listinfo/muscle
>>  <http://lists.drizzle.com/mailman/listinfo/muscle>
>>
>>
>>
>>  _______________________________________________ Muscle mailing list
>>  Muscle at lists.musclecard.com
>>  http://lists.drizzle.com/mailman/listinfo/muscle
>>
>>  -- This message has been scanned for viruses and dangerous content by
>>  MailScanner, and is believed to be clean.
>>
>>
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> Muscle mailing list
> Muscle at lists.musclecard.com
> http://lists.drizzle.com/mailman/listinfo/muscle
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.