Andreas Jellinghaus wrote: > but I have no clue how to write a new usb protocol.
Implementing a new USB device and driver is actually pretty easy. There is a lot of good development hardware, and libusb makes the PC software straightforward. Anyone looking into it, please stay away from the HID class and all other established classes, if you are not creating *exactly* that kind of device. Please make vendor-specific interfaces and just document them publically - then your device is as portable as possible. > some "ssl over usb" would be nice I was also thinking about this. Can USB be trusted? As an example, on SunRay thin clients there are USB connectors on the clients, but the device driver runs on the server; they proxy USB over TCP/IP. Oops. Also, consider KVM-over-ethernet switches, where $winadmin uses this new token to log in on the remote server. Oops again. One way to do SSL over USB would be to make the device into a USB network device, and just implement SSL on the device. Not great fun. Instead of a plug and play device driver, setup might then require network configuration by the user, and probably a browser plugin. > to authenticate device <-> pc What on the PC side would be authenticated by the device? > and allow other protocols on top of that. It does sound like the network device approach. But if PKCS#11 is what "we" need - then why not optimize hard for it.. //Peter _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
