Re: MUSCLE Mac Support
Ignorant question: (I'm not too familiar with Mac and OCF ;-) Are you building OCF on top of MUSCLE for Mac? Or are you building a PC/SC on top of an existing Mac OCF? The main reason for asking, is that I'd like to know if/how my Intertex IX36 driver for MUSCLE will port to Mac... The current version probably will, since it uses MUSCLES serial driver. But my next version (in progress) will support simultanous modem + reader operation, by using some pty/tty magic. And I doubt the Mac has pty:s. Will MUSCLE provide the reader drivers for the Mac? Morten At 14:03 1999-05-17 -0500, you wrote: Hi, I was looking into writing a PC/SC to OCF interoperability layer so that applications could talk using a C PC/SC like API which would JNI over to the OCF framework. This would be a quick hack for Macintosh users and all applications developed for Linux or Windows could quickly be ported to Macintosh and vice-versa. Any thoughts Dave *** 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 Mac Support
Hi, Most 'smart' readers should work on the Macintosh that used the serial interface that I provided. Readers that rely on line states will have some issues but not too terrible. What I was looking to do was place a C PCSC API ( Doug Barlow's SCard API ) that sits on top of OCF so that C based applications written for Unix or windows could easily be ported to the Macintosh. There is really not too much to interface. OCF requires the user to identify the card that is in use but PC/SC tries to take care of that itself - this does not always work so you can also specify which card you want to use in PC/SC. PC/SC tries to use the ATR as an identifying factor though this is not always accurate since many cards allow you to change the ATR etc. Due to poor ISO standards, this leaves the card management up to the user which human factors should tell us that is wrong. PC/SC does give you the options to use either method of connection though. If any of you will be attending the Linux Expo this next week please let me know. The MUSCLE site will probably be distributing OCF code and information soon. I would like to focus the site on 'Open Source Smartcard Initiatives'. I will discuss some future plans to interoperate PC/SC and OCF so we can cover a wide array of platforms using either an OCF Java interface or a C based PC/SC like interface. I should hopefully be distributing code for a couple of 'new' smartcard readers also. Thanks Dave * David Corcoran Internet Security/Smartcards Home: Purdue University 2252 US Highway 52 WestDepartment of Computer Science West Lafayette, IN 47906 CERIAS/COAST Laboratory Home: (765) 463-2455 Cell: (317) 514-4797 http://www.linuxnet.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 Mac Support
Hi, I know a company called Gravis (one of our customers) that do supply a special MAC Macintish Version of CHIDPDRIVE extern SmartCard terminal. Here is a link: http://www.gravis.de/pages/angebote/angebote_specials.html#cardreader The device can be ordered at: Gravis Franklinstraße 8 D-10587 Berlin Tel.+49/30/39022112 Fax +49/30/39022119 Mit freundlichen Grüßen, Thomas Kohn TOWITOKO electronics GmbH David Corcoran wrote: Hi, Most 'smart' readers should work on the Macintosh that used the serial interface that I provided. Readers that rely on line states will have some issues but not too terrible. What I was looking to do was place a C PCSC API ( Doug Barlow's SCard API ) that sits on top of OCF so that C based applications written for Unix or windows could easily be ported to the Macintosh. There is really not too much to interface. OCF requires the user to identify the card that is in use but PC/SC tries to take care of that itself - this does not always work so you can also specify which card you want to use in PC/SC. PC/SC tries to use the ATR as an identifying factor though this is not always accurate since many cards allow you to change the ATR etc. Due to poor ISO standards, this leaves the card management up to the user which human factors should tell us that is wrong. PC/SC does give you the options to use either method of connection though. If any of you will be attending the Linux Expo this next week please let me know. The MUSCLE site will probably be distributing OCF code and information soon. I would like to focus the site on 'Open Source Smartcard Initiatives'. I will discuss some future plans to interoperate PC/SC and OCF so we can cover a wide array of platforms using either an OCF Java interface or a C based PC/SC like interface. I should hopefully be distributing code for a couple of 'new' smartcard readers also. Thanks Dave * David Corcoran Internet Security/Smartcards Home: Purdue University 2252 US Highway 52 WestDepartment of Computer Science West Lafayette, IN 47906 CERIAS/COAST Laboratory Home: (765) 463-2455 Cell: (317) 514-4797 http://www.linuxnet.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 *** *** 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 ***