Its interesting, because of the need to enforce exclusive between the host and the guest- using 7816 controls (rather than any end-end crypto controls in GP).
Ive seen vmware seize the usb device entirely from the host, so (untrusted) host processes can no longer see the reader. However, the host OS also loads a custom vmware driver, to allow for this usb proxing of CCID, specifically. When vmware is running, it seems able to dynamically rebind its vmware ccid off of the already-enumerated usb endpoint, and then re-enumerate as a different device class (invoking the proxy driver on the host). In my tests, I'm afraid I was using muscletool, but it was compiled to use the Microsoft provider (on windows 2003), not pcsd on win32. The host was vista SP2 without UAC configured. After "too many" insertions, the vista/vmware usb/ccid bridge would get confused,and "lock up" the proxying configuration. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ludovic Rousseau Sent: Wednesday, November 19, 2008 12:19 AM To: MUSCLE Subject: Re: [Muscle] ccid new version 1.3.9 On Wed, Nov 19, 2008 at 12:32 AM, Peter Williams <[EMAIL PROTECTED]> wrote: > Tell more about the vmware virtual ccid. > > Is the driver that allows the guest OS to delegate to the reader in the host > machine? Yes. The CCID device in the host can be shared with the guest OS. On the guest OS the device is seen as a VMWare CCID device. I tried to use it on a Ubuntu host with a Debian guest but the virtual vmware reader was half working. The communication failed after the power up if I remember correctly. Someone reported a success with a Windows host and a Linux guest. So please test this feature and report. Bye -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
