Hello,
Here is sort of the itinerary for the distributed pcsc-lite:
First Release: Distributed pcsc-lite - you can make calls to remote
machines. If the client dies the server will disconnect the reader if and
only if you are the last one in the shared queue or if you are in exclusive
mode.
Problems: If you are doing a GetStatusChange the server can't accept any
more calls until the status change ends.
Second Release: Each call in the server will be threaded. Subsequent
calls will go into a calling queue and will be locked by a mutex if that
reader is in use by another call. This will fail if someone has performed
a begin transaction. The client will be called back on the GetStatusChange
function when a status change has occurred. This will allow the server to
accept multiple connections when the GetStatusChange function is called.
Third Release: This one will perform 3DES authentication between the server
and client. The server can choose to allow certain connections from users
at specific hosts, allow all, or deny some. The pipe will be encrypted
between the client and server using Secure RPC.
Eventually: Card abstraction will occur at the client side
The benefit ? Most Linux distributions include Sun RPC, Mac's and Windows,
and Java include ports of Sun RPC so no additional packages will be
required.
Let me know if you would like to see any additional features.
Best Regards,
Dave
David Corcoran
1008 Cherry Lane
West Lafayette, IN 47906
***************************************************************
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***************************************************************
