Daniel Silverstone <[email protected]> writes: >Note that, as the webpage explains, the device is a USB CDC device providing >an asychronous serial port.
Right, but you still need a driver on the host to provide the virtual serial port, e.g. FTDI's virtual COM port (VCP) or Prolific's USB-to-serial drivers (but obviously specific to the device that you're using). Or at least I've never found a USB-serial device that didn't need drivers on the host. >We chose this particular method of delivering the data stream because it was >well supported in most UNIX systems, along with Mac OS X and Windows, without >the need to write kernel drivers which would cause more concern among the >target market. Hmm, maybe we're talking about different things here... >The custom protocol which is implemented on top of the serial stream is >entirely there to ensure various security measures. Well, I guess this is your decision to make, but I think targetting the "I'm so paranoid I don't even trust my CPU unless I've built it myself from molecules" market seems to be rather limiting compared to "I just want a source of random noise that I can plug in and use". Peter. _______________________________________________ cryptography mailing list [email protected] http://lists.randombit.net/mailman/listinfo/cryptography
