Jump to content

Saryon

Members
  • Content Count

    5
  • Joined

  • Last visited

About Saryon

  • Rank
    Newbie

Recent Profile Visitors

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

  1. ok......i really don't understand the replies...one says 'install the drivers on one pc and it will work on all' where installing on one pc is already the problem and it's not logical that the bunny will then run on all others after this. and the next says to use the bunny on kali when 99.99% of the attack surface is windows... guys, how can i get the bunny to run on Windows if Windows (2x 7, 1x 10, fully updated) both don't support the ethernet rndis driver? the whole idea is that i don't need a driver to run the bunny because most of the time to do that, (at least local) admin rights are needed and i have yet to see any company using local admin for all users.
  2. Hi Apogee, I have tried with and without the USB cable. No significant difference... I have tried it on a third Windows machine now, again, the same: the RNDIS driver is not installed. I have manually installed the SERIAL drivers from the USB drive (for each switch-setting, I had to install the drivers again) but the RNDIS driver I cannot install because it does not have the driver on the USB and searching for it online causes Windows to say that it cannot find the drivers. So yeah, I am thinking logically. I am just hitting dead-ends because of lack of driver support.
  3. Thanks @Dave-ee Jones, for the response. Sadly, this means that the Bunny will not run out-of-the-box as an ethernet device. And, when attacking random systems, that means that the Bunny will not work as advertised and renders it essentially useless except as a Ducky-with-storage device. And the reason I had SERIAL, STORAGE and RNDIS_NETWORK configured was so I can debug why I could not get the networking part to work on MacOS. I didn't want to arm it (add extra functionality), I wanted it to work over the network and without serial, I couldn't connect to it as SSH didn't start up.
  4. Hi Kel, I followed as much as I could. But, because of the problems I'm experiencing, I cannot do step 5 & whatever comes after because Windows doesn't recognise the Bunny and MacOS does not allow forwarding from 172.16.64.1 over 172.16.64.64 it seems. Not even with factory default payload.txt's. But the steps have nothing to do with the steps mentioned there as it's a hardware recognition issue.
  5. Hi, I just received my Bash Bunny a few days ago and I've been tinkering around with it. It seems, to me, to be quite buggy: - Windows does not recognise the RNDIS interface at all. Not on Windows 7, not on Windows 10. - On MacOS, the ethernet interface *sometimes* works, sometimes it doesn't. When it does work, *sometimes* it is possible to connect to the Bunny using, quite often, SSH doesn't start up even though FTP and other services are running. This even after a few minutes waiting. - The serial interface often conflicts with having network & storage together, resulting in nothing happening or giving only access to storage. (I did this by adding "SERIAL" to the standard payloads already on the Bunny) - Using the manuals found online for network sharing (MacOS Internet sharing through 172.16.64.64), I cannot access the internet from the Bunny, so I cannot update it. On Windows, that's entirely out of the question as Windows does not even recognise the RNDIS network device. Windows gives the following message on the RNDIS driver: The drivers for this device are not installed. (Code 28) There are no compatible drivers for this device. To find a driver for this device, click Update Driver.
×
×
  • Create New...