Jump to content

maehko

Active Members
  • Posts

    11
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

maehko's Achievements

Newbie

Newbie (1/14)

  1. I just switched to ECM_ETHERNET and verified the same behavior on MacOS
  2. Thank's @snowc. That matches my experience as well. Does your LED change from purple to white after 2 minutes?
  3. I did see Darren's post before posting this thread and I have been able to duplicate that behavior. The problem described here though is affecting switch 1 as well and is NOT that the RNDIS doesn't automatically install due to it being a composite device. The problem that is occurring in both switch positions is that Windows cannot enumerate the composite devices when all three devices are specified via the ATTACKMODE command. Can someone else run the following payload and report your experience? LED R B ATTACKMODE STORAGE SERIAL RNDIS_ETHERNET LED R G B
  4. I've been trying to setup the bunny to work with RNDIS_ETHERNET STORAGE Serial but without success. The combination of any two of those selections works as expected, but any ordered combination of those 3 fails to mount any one of the three devices on M$ Surface, Win10 10.0.14393 Using the Payload.txt below, after the 7 second boot cycle, the LED turns purple and stays purple for 113 seconds, after which the LED turns white, but no storage, serial, or network device is present. After the LED has turned white however, device manager appears to refresh every so often like it's trying to enumerate new devices, but none show up. I'm not finding any relevant event log entries. Are their any persistent logs available via arming mode serial? #!/bin/bash LED R B ATTACKMODE STORAGE SERIAL RNDIS_ETHERNET LED R G B
×
×
  • Create New...