7 Commits

Author	SHA1	Message	Date
Alon Levy	5ed4050992	server/smartcard: don't push our own error on reader add ... The device already sends one. There are actually two connections going on: server to client - this is the smartcard channel, it reuses the VSC protocol. server to device - this is an internal connection using VSC too. We generally just passthrough all messages from the client to the device, and from the device to the client. We only rewrite the reader_id because the device knows about a single id (it is actually a card id), and we may manage more then one in the future. Bottom line is that there was an extra VSC_Error message reaching the client.	2011-02-10 10:34:53 +02:00
Alon Levy	0d6550ed60	server/smartcard: ignore VSC_Init from client	2011-02-10 10:34:42 +02:00
Alon Levy	21d1ec600b	server/smartcard: print instead of assert on bad reader_id in smartcard_char_device_on_message_from_device	2011-02-10 10:34:37 +02:00
Alon Levy	b05c744f4a	server/smartcard: libcacard uses network byte order, so we must too	2011-02-10 10:34:32 +02:00
Alon Levy	ed5e2fc942	server/smartcard: libcacard removed ReaderAddResponse	2011-02-10 10:34:16 +02:00
Alon Levy	efa3704dbc	server/smartcard: s/reader_id_t/uint32_t/ (libcacard changed)	2011-02-10 10:20:49 +02:00
Alon Levy	d99ec6c35b	smartcard: server side (not enabled yet)	2010-12-07 13:31:42 +02:00