MUSCLE Hello to this M.U.S.C.L.E. mailing list

I just joined the mailing list and wanted to say hello... I've been looking at the PC/SC specs and it looks like a good project. -- "Those who do not understand Unix | are condemned to reinvent it, | Mark Jackson poorly." | Software/

MUSCLE PC/SC implementation thoughts...

understand Unix | are condemned to reinvent it,| Mark Jackson poorly." | Software/Hardware Design -- Henry Spencer | email:[EMAIL PROTECTED] *** Linux Smart Card Developers - M.U.S.C.L.E. (

MUSCLE PC/SC implementation with GGI

I was looking at the GGI specs keeping in mind the PC/SC specs. It seems that GGI defines a "display" console as a pair - a monitor and an input device. Other input devices, such as a mouse are optional. I'm thinking that a sc reader would probably fit into the definition of a GGI "display" nic

Re: MUSCLE PC/SC implementation thoughts...

Jan Iven wrote: > A generic 'command line > interface' to the reader over tty would be broken at the first program that > doesn't understand the special tty stuff. Good point... > Right. However, I believe that a resource manager with only local entry points > is still needed. Any kind of conn

MUSCLE Kernel support for readers?

Has anyone done some work into this? These are my thoughts... 1. /dev/smartcard should be a valid kernel device. Not all readers are serial based, and so a symlink to /dev/cua* may not work in all cases. Security for such devices that are symlinked may be an issue... 2. At the same time, a