BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] code for hacked USB drive (BadUSB) released on Github
- Subject: [Discuss] code for hacked USB drive (BadUSB) released on Github
- From: drew.vanzandt at gmail.com (Drew Van Zandt)
- Date: Mon, 6 Oct 2014 11:13:19 -0400
- In-reply-to: <5432B010.8070201@gmail.com>
- References: <54323F84.2000306@gmail.com> <5432B010.8070201@gmail.com>
It is, however, not difficult to have a USB device reset itself and then change its answer when re-initialized. *Drew Van Zandt* On Mon, Oct 6, 2014 at 11:06 AM, Richard Pieri <richard.pieri at gmail.com> wrote: > On 10/6/2014 3:06 AM, Tom Metro wrote: > > If these drives look like an ordinary USB storage drive when first > > attached, I wonder what they are using as a trigger to have them switch > > They don't switch. A USB device can be only one kind (class) of device > at a time. This is set when the device is initialized with the root hub. > > -- > Rich P. > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://lists.blu.org/mailman/listinfo/discuss >
- Follow-Ups:
- [Discuss] code for hacked USB drive (BadUSB) released on Github
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] code for hacked USB drive (BadUSB) released on Github
- References:
- [Discuss] code for hacked USB drive (BadUSB) released on Github
- From: tmetro+blu at gmail.com (Tom Metro)
- [Discuss] code for hacked USB drive (BadUSB) released on Github
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] code for hacked USB drive (BadUSB) released on Github
- Prev by Date: [Discuss] code for hacked USB drive (BadUSB) released on Github
- Next by Date: [Discuss] code for hacked USB drive (BadUSB) released on Github
- Previous by thread: [Discuss] code for hacked USB drive (BadUSB) released on Github
- Next by thread: [Discuss] code for hacked USB drive (BadUSB) released on Github
- Index(es):