[Muscle] usb-skeleton.c in LDD3 can't be compiled in Kernel 2.6

2005-05-27 Thread mail mail
hi, everyone I try to compile usb-skeleton.c which is the example code in Linux Device Driver 3rd version using its own Makefile. But it doesn't work. (I am using Mandrake. "uname -a" = Linux localhost 2.6.3-7mdksmp #1 SMP Wed Mar 17 14:24:28 CET 2004 i686 unknown unknown GNU/Linux) [EMAIL PROTEC

Re: [Muscle] Solaris/SunRay PCSC support

2005-05-27 Thread Corcoran David
Vincent, The PC/SC bypass talks directly to the low level Sun Ray terminal API's and the PC/SC shim talks to SCF which talks to OCF. Basically the bypass library skips over SCF & OCF and talks to the Sun Ray terminal API Thanks, Dave On May 27, 2005, at 12:31 PM, Vincent Diluoffo wro

[Muscle] Solaris/SunRay PCSC support

2005-05-27 Thread Vincent Diluoffo
1) I'm looking for information about the difference between the SunRay server software 2.0/3.0 PC/SC bypass package and the muscle PC/SC shim for SCF. Are these the same or different in how they work and which is the recommended one? 2) Are these equivalent to a specific version of PC/SC lite? Tha

[Muscle] build problem on Solaris 9

2005-05-27 Thread Vincent Diluoffo
Thanks for the information. I was missing "as" from a package. Note: Solaris ships with everything you need, except for the compiler. All this stuff lives in /usr/ccs/bin and /usr/ccs/lib. If you still can't find it, make sure you have the following packages installed on your system: for tools (s

Re: [Muscle] build problem on Solaris 9

2005-05-27 Thread Douglas E. Engert
gcc is trying to call the assembler as. It looks like the gcc is expecting it at /usr/ccs/bin/as This directory has the Solaris development tools do you have this package installed? Vincent Diluoffo wrote: I have downloaded both pcsc lite 1.2.9 rel 7 and pcsc lite 1.2 with the same error. I hav

Re: [Muscle] PAM globally fixed cert and key number

2005-05-27 Thread Karsten Ohme
Bruce Barnett wrote: The goal is to disburden the user and to have self administrating systems. (E.g. I hate to disperse my public keys in SSH for public key authentication. My login in the network is everywhere the same, but I have a separate home directory.) When I authenticate myself with a

Re: [Muscle] supporting transactions in reader driver

2005-05-27 Thread Nikolay Elenkov
Nikolay Elenkov wrote: To answer my own question: ... muscleTools connects with MSC_SHARE_SHARED which causes the APDU's to be routed to IFDHControl instead of IFDHTransmitToICC. After changing MSC_SHARE_SHARED to MSC_SHARE_SHARED everyting worked nicely. (Cf. [00 a4 04 00] 06 [a0 00 00

Re: [Muscle] PAM globally fixed cert and key number

2005-05-27 Thread Bruce Barnett
>The goal is to disburden the user and to have self > administrating systems. (E.g. I hate to disperse my public keys in SSH > for public key authentication. My login in the network is everywhere the > same, but I have a separate home directory.) When I authenticate myself with a local system