Re: MUSCLE New to list, problems with PIN code ! ...
Hi, --- Christoph Plattner <[EMAIL PROTECTED]> wrote: > I have spoken with Towitoko, and it seems to be a > wrong > card in the the package. The label on the crad > package > says CHIPCARD M2 (I2C EEPROM) card, and Towitoko > says, that cards > using PINs are CHIPCARD M2P. The M2 type does not > use any > PIN. It's not the first time that somebody reports something about cards from Towitoko with wrong label on this mailing list. > > The information of the "000" as default PIN would be > helpful for me, but no chance any more to try it !!! > "000" is this always for new manufactured cards ? > Is it 0x00 0x00 0x00 binary or "000" = 0x30 0x30 > 0x30 ASCII ? > It's 0x00 0x00 0x00. This is true for 2-wrire and 3-wrire cards I have got from Towitoko, but I don't know if it aplies to other cards/manufacturers. __ Do You Yahoo!? Spot the hottest trends in music, movies, and more. http://buzz.yahoo.com/ *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE New to list, problems with PIN code ! ...
I have spoken with Towitoko, and it seems to be a wrong card in the the package. The label on the crad package says CHIPCARD M2 (I2C EEPROM) card, and Towitoko says, that cards using PINs are CHIPCARD M2P. The M2 type does not use any PIN. The information of the "000" as default PIN would be helpful for me, but no chance any more to try it !!! "000" is this always for new manufactured cards ? Is it 0x00 0x00 0x00 binary or "000" = 0x30 0x30 0x30 ASCII ? With friendly regards Christoph Carlos Prados wrote: > > Hi, > > > which includes 2 memory cards. Those two cards seems > > to be of a different type: > > - 2Kbit I2C EEPROM Card (256 Byte, R/W) > > seems to be a 2-wire card > > (icc->type = 2) > > If it's I2C, then it isn't 2-wire. If the Towitoko > driver assigns '2' to the ICC type then it migth be an > 2-wire card. > > > - 16Kbit I2C EEPROM Card (2048 Byte, R/W) > > seems to be a IC2 SHORT card > > (icc->type = 0) > > > > I don't know why these cards of different sizes are > > also > > of different types... ? > > > > Because of the protocol used to communicate with the > card is diferent. > > > But now to the problems: > > The ATR of the 16Kb card is always empty (NULL > > pointer, > > as it is no 2-/3-wire card). Is this implementation > > in the CT code correct ? > > > > Yes. I2C cards does not return ATR. So The driver > leaves this data blank. The CT spec does not says > nothing about this being incorrect, so I guess it's > fine. > > > And now the main problem: > > - > > > > The 2Kbit card seem to need the PIN code, is this > > correct > > Yes, you need to enter a PIN. The cards that come with > the beginers pack use to have PIN=000. > > >(I cannot write on it, and I saw in the > > code, > > that on type==2 and 3 cards, the PIN entering is > > always done. > > I have not seen any PIN (in the package, on the > > card, > > etc) So I don't know any key, and now the card > > always > > blocks PIN entering, as the retry counter is already > > on '0'. > > This is because somebody (I don't mean you ;-) entered > a wrong PIN 3 times, or because the card is bad. > > > Can I do here anything ? > > I also want to contact TOWITOKO (german company), > > the cards > > and card reader are coming from. > > > > If the card is actually blocked, you cannot. > > > Please help. > > I will further study the code to understand the PIN > > protocol > > and PIN handling. I have not found the spec for the > > security > > (PIN) handling and protocol yet. > > > > I don't know of such specification. You just need to > use the appropiate CT commands (see MKT specs) to send > PIN, change PIN, etc. > > __ > Do You Yahoo!? > Spot the hottest trends in music, movies, and more. > http://buzz.yahoo.com/ > *** > Linux Smart Card Developers - M.U.S.C.L.E. > (Movement for the Use of Smart Cards in a Linux Environment) > http://www.linuxnet.com/smartcard/index.html > *** -- --- private:[EMAIL PROTECTED] company:[EMAIL PROTECTED] *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE New to list, problems with PIN code ! (fwd)
Hi, > which includes 2 memory cards. Those two cards seems > to be of a different type: > - 2Kbit I2C EEPROM Card (256 Byte, R/W) > seems to be a 2-wire card > (icc->type = 2) If it's I2C, then it isn't 2-wire. If the Towitoko driver assigns '2' to the ICC type then it migth be an 2-wire card. > - 16Kbit I2C EEPROM Card (2048 Byte, R/W) > seems to be a IC2 SHORT card > (icc->type = 0) > > I don't know why these cards of different sizes are > also > of different types... ? > Because of the protocol used to communicate with the card is diferent. > But now to the problems: > The ATR of the 16Kb card is always empty (NULL > pointer, > as it is no 2-/3-wire card). Is this implementation > in the CT code correct ? > Yes. I2C cards does not return ATR. So The driver leaves this data blank. The CT spec does not says nothing about this being incorrect, so I guess it's fine. > And now the main problem: > - > > The 2Kbit card seem to need the PIN code, is this > correct Yes, you need to enter a PIN. The cards that come with the beginers pack use to have PIN=000. >(I cannot write on it, and I saw in the > code, > that on type==2 and 3 cards, the PIN entering is > always done. > I have not seen any PIN (in the package, on the > card, > etc) So I don't know any key, and now the card > always > blocks PIN entering, as the retry counter is already > on '0'. This is because somebody (I don't mean you ;-) entered a wrong PIN 3 times, or because the card is bad. > Can I do here anything ? > I also want to contact TOWITOKO (german company), > the cards > and card reader are coming from. > If the card is actually blocked, you cannot. > Please help. > I will further study the code to understand the PIN > protocol > and PIN handling. I have not found the spec for the > security > (PIN) handling and protocol yet. > I don't know of such specification. You just need to use the appropiate CT commands (see MKT specs) to send PIN, change PIN, etc. __ Do You Yahoo!? Spot the hottest trends in music, movies, and more. http://buzz.yahoo.com/ *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
Re: MUSCLE New to list, problems with PIN code ! (fwd)
On Mon, 18 Jun 2001, David Corcoran wrote: > -- Forwarded message -- > Date: Sun, 17 Jun 2001 02:14:01 +0200 > From: Christoph Plattner <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: New to list, problems with PIN code ! > > Hello SmartCard Linux hackers ! Hi! > I have recently bought a package from TOWITOKO > > CHIPDRIVE linuxpack > > which includes 2 memory cards. Those two cards seems > to be of a different type: > - 2Kbit I2C EEPROM Card (256 Byte, R/W) > seems to be a 2-wire card > (icc->type = 2) > - 16Kbit I2C EEPROM Card (2048 Byte, R/W) > seems to be a IC2 SHORT card > (icc->type = 0) > > I don't know why these cards of different sizes are also > of different types... ? Why not? > But now to the problems: > The ATR of the 16Kb card is always empty (NULL pointer, > as it is no 2-/3-wire card). Is this implementation > in the CT code correct ? A memory card does return no ATR... In fact, the reader might return one, if it wants to... > And now the main problem: > - > > The 2Kbit card seem to need the PIN code, is this > correct (I cannot write on it, and I saw in the code, Yes, memory cards can have PIN codes entered. The method used to enter this PIN is 'implementation defined', i.e. you should ask your card manufacturer. > that on type==2 and 3 cards, the PIN entering is always done. > I have not seen any PIN (in the package, on the card, > etc) So I don't know any key, and now the card always > blocks PIN entering, as the retry counter is already on '0'. > Can I do here anything ? If this is a real PIN code, and the card can't be reset, too bad... Good luck! -- Erwann ABALEA [EMAIL PROTECTED] RSA PGP Key ID: 0x2D0EABD5 - No wanna work. Wanna bang on keyboard. *** Linux Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/smartcard/index.html ***
