Comment Re:This is great. (Score 1) 36
> you're really splitting hairs, that's not what is meant. a serial port is very much the physical rs232 "connector" or an emulation of it.
Key word "or an emulation of it." From the software point of view, all it's doing is sending and receiving bits at some baud rate. The physical hardware interface no longer matters. That's kind of the whole point of these things. Beyond the hardware interface, modern keyboard and mouse speak exactly the same protocol as they have since the PS/2 days. In fact USB keyboards usually still have PS/2 port hardware in them, which is why you can use those USB-PS/2 adapters (which are entirely passive).
They don't "identify as" serial devices. The are serial devices. Always have been. It's not unthinkable that a poorly made device could be vulnerable to a firmware hack and not unthinkable that giving javascript access to serial ports could be a vector for such an attack. Not even hard to imagine a fancy keyboard with programmable RGB lights or OLED displays (that definitely have microcontrollers capable of executing arbitrary code) getting exploited.
> of course, which is why the browser asks the user for permission to acces all these devices!
That's a strange way to admit you don't know how security vulnerabilities work. "There's no way someone could get in uninvited; there's a lock on the door!"
> they can already do that.
Maybe? But adding a system where javascript can directly and explicitly interact with serial ports is definitely not going to make doing it any harder, is it?
=Smidge=