Michal Labedzki
changed
bug 8131
Comment # 1
on bug 8131
from Michal Labedzki
There is no possibility to recognize that device as MassStorage.
1. Class/Subclass/Protocol is 0/0/0 so use class code from Interface
Descriptors, but we do not have them. So do not know that Mass Storage
dissector should be used (only it checks bytes mentioned by you)
By the way, I am not expert too, but maybe we can obtain needed data in the
same way like DEVICE DESCRIPTORs when start dumping.
2. We can add recognize by VendorId/ProductId, but to do that there is a need
to update massStorage dissector to support that way (currently - "crash", I
will try to fix that). I guess we can try to add all known device manually..
why not... of course this is task for years. But there is one problem...
Devices where Class/Subclass/Protocol is 0/0/0. Maybe some endpoints are
something else then Mass Storage?
3. Last time I add support for decoding by three ways - usb.device
(busID/deviceAddress), usb.protocol (Class/Subclass/Protocol), usb.produce (by
VendoirID/ProductID). Next step is creating DecodeBy for USB - I am working on
that. I think this is the best solution here. There is a need to add Decoding
by Endpoints too. (I am thinking about DecodingBy for Bluetooth over USB too)
>From my point of view there is no a bug. And DecodeBy for USB is the easiest
solution. Better ideas?
Could you request to add your device info to usb.ids? I see that your
MassStorage Device is "idProduct: "Unknown (0x50a1)". Try:
"lsusb -vd 0bc2:50a1 | head -n 16" and create new request ("Add item") here:
https://usb-ids.gowdy.us/read/UD/0bc2
You are receiving this mail because:
- You are watching all bug changes.
