"Daniele B." <my25mb@has.im> wrote:
> > uaudio0, ugen1. Is it possible it could be manipulated to act as a
> > USB keyboard or some other kind of potentially dangerous USB input?
> >
>
> I guess the question can be turned in: what does OpenBSD under the
> wood to avoid uaudio0 or ugen1 get transformed in a nice passage to
> hack my whole system? Eg. I know some of us go around with OpenBSD on
> usb sticks but our equipment on the desk is safe from usb tools like
> eg. micro usb equipment inserted in our usb hub? What countermeasure
> OpenBSD have to these kind of physical penetrations using the usb
> stack? Finally are uaudio but mainly ugen stress tested to avoid that?
>
Eventually this could also help:
wiz$ usbdevs
Controller /dev/usb0:
addr 01: mine:---- Intel, xHCI root hub
addr 02: mine:---- VIA Labs, Inc., USB2.0 Hub
addr 03: mine:---- SunplusIT INC., HD WebCam
addr 04: mine:---- ?????\^A??, ?????\^A??
addr 05: mine:---- NEC, hub
addr 06: mine:---- Dell, Dell USB Wired Entry Keyboard
addr 07: mine:---- Sunplus, USB Optical Mouse
addr 08: mine:---- VIA Labs, Inc., USB3.0 Hub
addr 09: mine:---- JMicron, USB to ATA/ATAPI Bridge
addr 10: mine:312b ADATA, ADATA USB Flash Drive
Controller /dev/usb1:
addr 01: mine:---- Intel, EHCI root hub
addr 02: mine:---- Intel, Rate Matching Hub
usbdevs -v could be more verbose too.
Indeed, in my case addr 04 is a unknown device to me.
wiz$ usbdevs -v -a 04
addr 04: 0489:e04e ?????\^A??, ?????\^A??
full speed, self powered, config 1, rev 0.01, iSerial
?????\^A??
driver: ugen0
Then:
wiz# dmesg
[..]
ugen0 at uhub0 port 4 "?????\^A?? ?????\^A??" rev 1.10/0.01 addr 4
uhub3 at uhub0 port 5 configuration 1 interface 0 "NEC hub" rev
2.00/1.00 addr 5 uhidev0 at uhub3 port 1 configuration 1 interface 0
"Dell Dell USB Wired Entry Keyboard" rev 1.10/1.78 addr 6
I see this unknow device is the ugen0 of the usb hub where my mouse
is attached etc.
Any further help?
-- Daniele Bonini
No comments:
Post a Comment