|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: [Muscle] can not write in SLE4428
From: Serge Koganovitsch (serge.koganovitsch
zetes.com)
Date: Fri Feb 25 2005 - 07:00:44 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
Since PC/SC is able to read the ATR, it means that your card is
an asynchronous card, not a synchronous card.
There are some memory cards that can be 'Asynchronously' accessed using PC/SC.
Looking at the ATR, it seems to me you have a STARCOS S21 card.
You should probably use the STARCOS APDU's instead of the SLE4428 ones ?
Regards,
Serge
On Thursday 24 February 2005 20:42, Abhijeet Mamarde wrote:
>
> hi,
>
> I am final year engineering student and i am making a smart card
> application for the student on Linux platform as my project.
>
> So, for that i had brought Castles Technologies EZ100PR (serial) smart
> card reader. Actually i had brought one PC BASED SMART CARD SDK from
> MTECH (Pune, India) company. Accompanying with it there was two smart
> cards.
>
> I had tried, a lot to understand how to read/write data from/to smart
> card. I am using the pcsclite version 1.1.1. But then i come to know
> that the smart card which i had is actually the logic card i.e. it is
> not the smart card satisfying the T=0 or T=1 protocol.
>
> This is obivious from the ATR (Answer To Request) of my cards. The ATR
> of my cards is 24 bytes long. It is as follows :
>
> 1. (hex) 0x3b - (dec) 59 - ;
> 2. (hex) 0xbf - (dec) 191 - +
> 3. (hex) 0x18 - (dec) 24 -
> 4. (hex) 0x 0 - (dec) 0 -
> 5. (hex) 0x80 - (dec) 128 - Ç
> 6. (hex) 0x31 - (dec) 49 - 1
> 7. (hex) 0x70 - (dec) 112 - p
> 8. (hex) 0x35 - (dec) 53 - 5
> 9. (hex) 0x53 - (dec) 83 - S
> 10. (hex) 0x54 - (dec) 84 - T
> 11. (hex) 0x41 - (dec) 65 - A
> 12. (hex) 0x52 - (dec) 82 - R
> 13. (hex) 0x43 - (dec) 67 - C
> 14. (hex) 0x4f - (dec) 79 - O
> 15. (hex) 0x53 - (dec) 83 - S
> 16. (hex) 0x20 - (dec) 32 -
> 17. (hex) 0x53 - (dec) 83 - S
> 18. (hex) 0x32 - (dec) 50 - 2
> 19. (hex) 0x31 - (dec) 49 - 1
> 20. (hex) 0x20 - (dec) 32 -
> 21. (hex) 0x43 - (dec) 67 - C
> 22. (hex) 0x90 - (dec) 144 - É
> 23. (hex) 0x 0 - (dec) 0 -
> 24. (hex) 0x9b - (dec) 155 - ¢
>
> So I had called back to the person from the same company and asked him
> about the type of the card. He told me it is SLE4428. After this
> information i had again tried to read the data. Now I can read it. (1024
> bytes). But now i am unable to write the data.
>
> After searching, i again come to know that these cards has 2 byte long
> PSC (Programmable Security Code) which must be verified before any write
> operation is performed. So, I again search for the PSC code for the test
> cards i.e. the cards which is send for the first time.
>
> So somewhere I read that it is 0xFE 0xFF for the test cards. But it is
> not in my case.
>
> So, can anybody please help me to solve this problem ???
>
> Any help is welcomed
>
> Thanx for your help in advance
>
>
>
>
> <http://clients.rediff.com/signature/track_sig.asp>
>
_______________________________________________
Muscle mailing list
Muscle
lists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]