Re: MUSCLE Problems with serial communication / cardreader ECO5000
Hi, I already used the "root"-account. But this doesn´t seem to help... Bye, Frank -Ursprüngliche Nachricht- Von: Michael Renzmann [EMAIL PROTECTED] An: [EMAIL PROTECTED] [EMAIL PROTECTED] Datum: Mittwoch, 18. August 1999 18:43 Betreff: Re: MUSCLE Problems with serial communication / cardreader ECO5000 Hi Frank. But the "serial.c" - file (provided with the CT-skeleton sources) doesn't seem to work. I get a handle to "/dev/ttyS0" for example, but other functions (like tcgetattr(handle, ...)) shutdown with an error (-1). Where is the problem ?? Trivial, but is your user allowed to send/receive data to/from the port? I eleminated a similar problem this way (in my special case I allowed everything to everyone). Hope that helps. 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 *** *** 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 Problems with serial comms
Frank, Try to use ltrace or strace to have the result of the opening functions with the port, it has helped me sometimes with the problems concerning the permisions, and other system calls. See you, Fer *** 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 ***
