Alright, so I'm starting in on this.
The plan is, as we discussed, for the spiceqxl_drv to create a fifo and
relay the smart card messages through that.
A new program, spice-ccid, will read those messages, and exchange the
appropriate protocol with pcscd, which should provide it through to
And, finally, if that's all right - on to the next question: where
should spiceccid fit in the XSpice stack? Should it be part of the Xorg
driver? Should it be a vd_agent process?
I'm not sure - I was thinking a third part, this time it's a bit more
complicated, basically having a pcscd
On 08/06/2014 06:14 PM, Jeremy White wrote:
And, finally, if that's all right - on to the next question: where
should spiceccid fit in the XSpice stack? Should it be part of the Xorg
driver? Should it be a vd_agent process?
I'm not sure - I was thinking a third part, this time it's a bit
On 07/25/2014 12:01 AM, Jeremy White wrote:
I think I have a tentative, but sufficient grasp of how the Smart Card
stuff flows from the client into the server. It's not quite as clear
how the server bridges it into qemu, but I think I have the gist of it.
However, that doesn't work for
Thanks!
I'm going to mostly repeat what I think you just said to make sure I
understand you; please correct me if I get it wrong.
Yes. But just note that spice-server doesn't do anything except move
bytes around. The actual protocols involved are:
qemu: ccid protocol: usb smartcard reader
I think I have a tentative, but sufficient grasp of how the Smart Card
stuff flows from the client into the server. It's not quite as clear
how the server bridges it into qemu, but I think I have the gist of it.
However, that doesn't work for XSpice sessions.
I'm not sure why it shouldn't.
On 07/22/2014 12:41 PM, Jeremy White wrote:
I'm hoping to get some guidance / clue bats / shock and horror in
implementing Smart Card support for XSpice clients.
I think I have a tentative, but sufficient grasp of how the Smart Card
stuff flows from the client into the server. It's not quite
