Re: MUSCLE Towitoko Chipdrive Problems
Hi Richard. My Problem: With the Chipdrive Extern 2.0 (Towitiko) everything is OK. When I use the ChipDrive Extern 4.3 I have some Problems. I get a wrong cardStatus sometimes. I flush the serialport, befor I send the command (0x03; 0x07) The response is most (0x00, 0x80, 0x40 or 0xC0), but sometimes it is 0x50, or something else ( not 0x20). Just test if the corresponding bits are set or not, do not depend on the whole return value of the reader. Corresponding means: those bits, that form the values stated in the chipdrive documentation. I don´t have them in mind as I haven´t working with it for a while. richard Bye, Mike *** 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: R: MUSCLE SSP for Cyberflex
Hi. Some of the crypto functions may require a significant increase in the WWT on the reader. If you let me know what reader you are using I can see if this will be a problem and fix it before it exists. Could you please explain me what "WWT" stands for, because I don't understand what the problem is. However, I'm using a Towitoko's CHIPDRIVE. WWT stands for "Work Waiting Time". This is a time span that can be set from the PC which is used to wait for a response of the card after sending a command. If the WWT has times out, a failure is assumed. Crypto functions in smartcards need some time, so small WWT values can cause the PC to suppose an error even if there is none (the card is still working on the crypto). Bye, Mike *** 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 MakeSolo for Cyberflex Access / JC2.1 ?
Hi. - Is this mailing-list dead ? The latest archived message is from Mon, 12 Apr 1999. It is definately not dead. I received a bunch of mails in the last weeks. cu, Mike *** 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 Reprograming handy-card
Hi. I'm looking for a solution to reprogram my handy-sim-card. I've heard, it is possible to got more space for sms while have less space for telephone-book. I have also a chip-drive (micro) from towitoko. Is this possible and is this the right mailing-list? In general, it is possible to tweak the sim-card as you described it. In particular it will be some work to realise a program that does this. I don´t know how far David is with the implementation of the T=0 protocol which is needed for this task. If not in the pc/sc-library, then you could use the driver that Carlos Prados has written, they support T=0. The URL can be found on the MUSCLE website. The Towitoko-reader can be used for this task. But if I understood you correctly, you are looking for a program that does this work for you, right? Or do you want to program it on your own? IIRC there is a program available from Towitoko that can do this, but it will cost "some" money and runs on Windows only. Thx, Reinhold cu, Mike *** 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 ChipDrive Micro Reader
Hi. And here I come. :) I had only I2C and 2Wire reading working and never got writing to work with the information provided by Towitoko on their website. I found some time ago how it really works, thought "how braindamaged" and deleted the memory card reading support from the library. It seems that the support for memory cards using Chipdrives is hard to program. The URL (of my lib) is http://www.franken.de/crypt/scez.html. Ok, now I will bookmark it at least twice, so I´ll find it the next time I´m searching it :)) cu, Mike *** 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 BOUNCE [Jan Iven j.iven@rz.uni-sb.de]
Hi. [...] Plus I have a little QT GUI app for reading i2c cards if anyone is interested. David, how do you find that much time to develop this bunch of code? :) cu, Mike *** 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 [Chris Zimman chris@supernova.underpass.com]
Hi. I was sniffing the serial port while Smartcard Explorer was running, it seems to be sending some commands that aren't listed in the doc. I've written to Towitoko regarding this, but as of yet, received no response. Towitoko told me at most 6 months ago that they plan to work over the whole documentation for their chipdrive family. Nothing happend until now. Regarding any information on their readers or any cards etc. their support is bad. Try writing a mail to Gerhard Poul, he is one of the authors of the Towitoko Driver Project (www.penguinteam.org/towitoko). He told me some months ago on some ideas he had to figure out the parameters of an i2c-card. cu, Mike *** 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 ChipDrive Micro Reader
Hi. Is there anybody here successful using Linux driver with Towitoko ChipDrive Micro Reader? Yes, but I wrote them myself ;) I baught one of this SmartCard reader from Autostart Singapore. It came with an example memory card, [...] But when I try with Linux driver written by Carlos Prados, the CT-API version 1.6.3, it error when try to reset and get ATR response from card. Other functions like activate, deactivate, set LED (even though this reader has no LED), and card detect work fine. That is one problem I had in the beginning, too. The answer to your question is simple. Carlos driver does only support one of five different mainstream protocol types, T=0. T=0 is used for processor cards, like GSM-SIM-Cards for mobile telefones. T=0 is one of two asynchronous protocols, the other is called T=1. Apart from this protocol family there is those of the synchronous protocols, which are used for memory cards. It consists of three members: 2-wire, 3-wire and I2C. I would guess that you have tried to use the memory card that was delivered with the reader with Carlos routines. That would be the same failure I made some months ago. This won´t work. You would need a driver that supports the protocol that the card speaks that you want to use. To determine which protocol a card speaks you can take the "smartcard explorer" from the Towitoko CD. For the i2c-protocol there is another library written by the "Towitoko Driver Project". For more information on that you should have a look at http://www.penguinteam.org/towitoko. Matthias Bruestle wrote a library that supports every Chipdrive family reader beside others and can handle synchronous protocols iirc. But I couldn´t find the right URL. He is reading this list, maybe he tells you :) I wrote my own lib that implements only T=1. There has been one release only yet and it had a lot of bugs. I didn´t had the time to finish work on the next version, especially on the documentation. Hope that helps a bit. cu, Mike *** 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 Power Up Failed
Hi. I've ordered 2 of these cards (ZC 2.4), and tested the demos with my reader (GCR410 from Gemplus). 1 card is already out of service, and doesn't answer to a reset... I only loaded the Calc demo app, tested it, it worked. I killed one ZC 2.3 by a wrong way of crc calculation. But this has been pointed out in the manual, it was a logical error of mine. Apart from this I never had problems with these cards, even while programming my own library with BC-specific functions and a set of tools that make extensive use of BasicCard functions. What software did you use to load the images into the card? Under which OS? On the other card, I loaded the Elliptic Curve demo, the demo works pretty well, and the card is still functionning. These cards seem very attractive, the Basic is not like the old Basics I used to program when I was 7... No, it is a procedural basic language and very powerful. But I find them too unstable... Because of this small problem you encountered? ;) cu, mike *** 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 Power Up Failed
Hi Hatto. It should work with a processor smartcard such as Cryptoflex. Do you or anyone else know where (in Germany) I can get a Cryptoflex or any other card which can be used with the Towitoko driver? Try out the BasicCard. An powerful processor card that can be used with Muscle as far as I know. It can be programmed with Basic, has DES/3DES encryption onboard, with new lib version even elliptic curve algorithm, cheap and you can order small numbers of those card. More information on http://www.zeitcontrol.de and http://www.basiccard.com. If you have problems programming the card, then send me a mail. I´ve some experiences, as I write my own library for card readers and this card. cu, Mike *** 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 ***
MUSCLE Re:
Hi. The new version allows you to connect up to multiple channels during the same session. For example you could connect to a smartcard reader in Germany and one in Japan ( up to 16 simultaneous connections ) Seems as if there is one who can read my thoughts :) Thats what I planned to realise with my own lib. Is it still possible to use local connections without RPC, or do you use RPC all the time regardless if the target reader(s) are local or not? There will also be a new reader driver soon that supports T=1. Did you use some of my code I sent you? If so, I had to send you the new version, as the old had a lot of bugs. Best Regards, Dave Bye, Mike *** 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 crypto JavaCard
Hi. IMO very good is the site of Zeitcontrol. SDKs and detailed documentation for download and cards can be ordered in any quantity. If only I knew BASIC better. So, their Basic isn´t that hard to learn. I programmed a lot with Basic some years ago, but switched over to C about two years ago. When I started programming the BasicCards, it was just like learning Basic from the scratch. But that really is no problem, if you find some time for it. cu, Mike *** 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 SSH and Smartcards?
Hi Eric. What about using a crypted communication between the reader and the card? That's no help. The secret would still be on the (untrusted) host for the ssh authentication. Yes, you´re right. I didn´t thought on that. Bye, Mike *** 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 ***
MUSCLE T=1 implementation
Hi. After I´ve found some severe bugs that caused heavy problems (and many sleeples nights :-) ) it seems that the routines are working. But there is a lot of work left. Currently there is no error handling done, that means that the T=1-routine won´t try to resynch to the card or something like that. If an error occurs, the routine leaves with only indicating that there was an error, but does not tell, which kind of error that is. I added support for generic commands of the BasicCard from ZeitControl (www.basiccard.com), that uses the T=1-protocol. The support for this card will be enhanced in the next weeks, I´ll tell more on that in a few days. If anyone wants to try the routines (David, you should have received them already), just send me a mail, as there is no place in the web you can find them. But be aware that there is no documentation yet (apart from some comments in the sources). They only work with Towitoko drives and with the current structure it will be some work to add support for further drives. I would be glad if someone tests my work as it is my first piece of programming using Linux and C (and Smartcards of course :)). Bye, Mike *** 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 fyi: towitoko bug
Hi Carlos. Have you tried to split one T=1 APDU into more than one fragment and send them secuencially to the reader? That´s not the real problem. You are right, that huge amounts of data can be split by using the block chaining mechanism of the T=1-protocol. The problem will be, if the card has an IFSC of 255 bytes and the programmer wants to use the whole range of the card´s receive buffer. By sending 255 bytes of information at once (255 bytes of real information, protocol data not included!), he has to send more than this 255 bytes to the reader because of the protocol overhead. Try to tell this to the reader by using one byte for "length of data to send" :-) Actually this problem can be solved by not using the whole receive buffer range of the card, as someone wrote here. But in order to avoid problems in special cases this problem has to be shown to programmers, I think. That´s the reason why I wrote this "bug report" within the mailinglist, as there should be some programers using Towitoko-readers :-) I think that if it is said that you can communicate transparently with the card by issuing (0x6f, nn, 0x05, qs, t1, t2, ...) commands, it should not matter how many fragments you use to send one APDU. As I wrote above: you are right, as long as you only look at the maximum length possible for one APDU. As soon as you add the protocol overhead (which has to be done... :) there will be more than 255 bytes to send via the drive. Bye, Mike *** 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 ***
MUSCLE basics (part 2)
Hi everybody. An addtition to the mail I wrote yesterday: I tried some memory cards under Win98. Using the Chipcard-Explorer shows, that some of these cards seem to send an ATR (AtrBinarySize 4, ATR differs from card to card as expected). Trying to get an ATR with exactly the same cards in the reader using the library of Carlos Prados, no ATR is returned by the reader. Using an processor card with these routines, an ATR _is_ returned. So the routines seem to be ok. Any ideas? Bye, Mike *** 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 ***
