GermanNoob

Active Members
  • Content count

    108
  • Joined

  • Last visited

1 Follower

About GermanNoob

  • Rank
    Hak5 Fan ++

Profile Information

  • Gender
    Male
  • Location
    Germany
  • Interests
    IT related: networks, security, defense
    others: golf, climbing, hiking
  1. Have you copied only the payload.txt from the library or everything within the tools_installer folder? You need to copy everything! I'm wondering what happens here... payload_installer does NOTHING on your host machine! Do you understand BASH scripts? Check the install.sh!
  2. OK let's work on one... So what exactly did you do while trying tools_installer and what happened. Please describe step by step, as probably you will have done something wrong and we need to find our what...
  3. @paimon Have you installed the actual GitHub version of the payloads? If yes, which payload are you trying to run? Which OS are you using?
  4. @Sami, you are partly right. The bunny_helpers.sh is updated but also the install.sh If somebody follows the instructions I posted before, everything should work fine as long as everybody does exactly these steps.
  5. Just follow these steps: Be sure to have the Bunny in an original state: Set BashBunny to arming mode Connect it to your computer Download the newest repository from GitHub Copy the GitHub repository to your BashBunny drive (at least the complete payload/librabry) screen into your BashBunny as described in wiki (Connecting to to the Bash Bunny Serial Console - http://wiki.bashbunny.com/#!index.md ) rm -r /pentest Exit BashBunny / screen Now install the tools: Copy the everything WITHIN the tools_installer folder to one of the switch folders Eject the Bunny from your host OS Remove the Bunny from the USB port Select the switch position to the one you copied the payload Connect your Bunny to the computer and just watch it running If the installation fails: Please be sure that you did all of the above steps Check and tell us what's within /pentest Describe in detail what you did (before) and what happened
  6. Hi @My Name Jeff these are the steps for recovery: Switch to arming mode (Switch3 nearest to USB) Plug the BashBunny into USB or an an power source Wait until the GREEN LED turns off (roundabout 3 secs?) Unplug the BashBunny Repeat step 2 - 4 another two times (which means: create three fail boots) replug the BashBunny and wait! The BashBunny will blink RED for about three minutes. DON'T UNPLUG IT!!!! The BashBunny will reboot; You're fine to work with it, when it blinks BLUE again...
  7. You're welcome, @GreenRubi
  8. Have you downloaded the newest version of all payloads (including bunny_helpers.sh) from GitHub? try the test I just described and tell us the result.
  9. That's really weird as I tested your first payload on my BashBunny & Computer and it works just fine... Have you tested the bunny_helpers.sh "offline" meaning without using in a payload? Just connect your Bunny and connect to it with screen or ssh Mount the payload drive to /root/udisk with mount -o sync /dev/nandf /root/udisk 3. goto /root/udisk/payloads/library 4. type "source bunny_helpers.sh" 5. type "echo $SWITCH_POSITION" That should work and tests your bunny_helpers.sh
  10. Sorry, @trumpet7347! Obviously I didn't read your post correctly... Having a look again to your code the problem is the brackets: ${SWITCH_POSITION} just try this: QUACK STRING Testing Switch Position, Switch Position is $SWITCH_POSITION
  11. You're welcome, @terrier
  12. OK, then let's do it step by step: Switch to arming mode (Switch3 nearest to USB) Plug the BashBunny into USB or an an power source Wait until the GREEN LED turns off (roundabout 3 secs?) Unplug the BashBunny Repeat step 2 - 4 another two times (which means: create three fail boots) replug the BashBunny and wait! The BashBunny will blink RED for about three minutes. DON'T UNPLUG IT!!!! The BashBunny will reboot; You're fine to work with it, when it blinks BLUE again...
  13. Tested it... Well it is: diskutil unmount /Volumes/BashBunny Works for me
  14. Hmm, what do you not understand of the description I posted ?
  15. I haven't tried it but probably you could do this with the terminal umount command...