> >> PS: I saw that the latest svn got rid of the SHM interface and uses >> sockets, very nice. This opens the possibility to make pcsc available >> over network easier than before.(I already thought about doing this...) > > That was one of the motivations for removing the shared memory. >
Do you have any implementation ideas? should the libpcsc read a config file where it should search for readers (locally, remote). I think its should use some ssl encryption too, but that can be left as a second step. I think the "communication context" should be done in seperate files, which needs an additional layer. Curently the subsystem only reports back a fd, is this enough or should there be more data (extend it to some struct)? It should work only with fds but it maybe to few information. I think the ltsp project implemented "remote usb sticks" and figured out a safe way that only the correct user can connect the usb daemon. But maybe the first step is "let connect everyone and do everything with the reader" Martin _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
