Ron4586
-
Posts
9 -
Joined
-
Last visited
Posts posted by Ron4586
-
-
17 hours ago, ZZZ_ said:
Could you explain how you did for your bashbunny to work again ?
I did exactly the same, it was in read-only after a fail with the tools installer, then I formatted, and now, my bashbunny can only be used as a usb ^^'
well I mainly use kali Linux on my computer although I do have separate windows computer after the bunny being read only in Linux I decided to attempt using the bunny in windows the kind person on here told me to see if I could still connect to serial on windows and I was able to and all the files were till in the bash bunny directory and I was able to rename my bashbunny bashbunny in windows even though its in all caps lol. then what I did once all that was there I downloaded the bashbunny master folder that Darren posted in the QuickCreds post in the forums the [PAYLOAD]Quickcreds one once I downloaded that folder I unzipped it and copied the payloads folder over to my Bunny which gave me the library switch 1 and switch 2. the Pentest folder I am at a loss at. I can run payloads though. Here is a tip about installing the tools now this is something I wasn't able to find on this site for help installing the tools. in the tools_install folder is the install.sh the readme.md and the payload ok. you don't want to name your payloads payload.txt just name it payload its already a .txt file if you name it payload.txt its really payload.txt.txt. That being said run the payload as it is named payload. once you run it your install.sh will change to install.sh.INSTALLED that is the secret to getting the tools installed then once I got that working the quick creds payload works. Just make sure all of your payloads are named payload. I am still having the read only problem in Linux I can still run the payloads I put on the bunny from windows but I can't modify or do any changes to the bunny in Linux since it says it is read only. I might just have to buy a new one. But that is how you properly install the tools_installer you can run it in switch 1 or switch 2 but I installed the toold in switch 2. hope that helps
-
ok update to my problem i can plug my bunny into a windows computer and transfer files as i please cut and paste into the bunny and i can even run payloads now the quick creds one works and all payloads work so far. The New problem is the bunny is only Read Only on my linux computer how do i resolve this problem?
-
26 minutes ago, Ron4586 said:
ok so i plugged my bunny into a windows computer and pulled up the serial root Bunny console and was able to log in to it and i typed those commands you said and they all have the rwxr-xr-x but they have a d in front of it so it says drwxr-xr-x 3 root root 4096 Dec 31 16:00 . then under that it says drwx------ 6 root root 4096 Dec 31 16:03 .. then under that it says drwxr-xr-x 2 root root 4096 Mar 11 2017 System Volume Information that popped up after i typed the mount-o sync /dev/nandf /root/udisk and the ls-la /root/udisk yet the bash bunny serial console still has all of the files in it when i type ls for directories its all there. but when i manually go into the bash bunny as a drive it just says drive D: isn't called Bash Bunny anymore and there is nothing on the bunny except System Volume Information and the contents inside that. So howcome all the Bunny files are still their in the linux serial console but i can't access anything on the bunny and it's not even called Bash Bunny anymore and it is still Read Only
i forgot to add in there that im still getting a Dirty Bit even though i have chosen to correct it it never goes away
-
ok so i plugged my bunny into a windows computer and pulled up the serial root Bunny console and was able to log in to it and i typed those commands you said and they all have the rwxr-xr-x but they have a d in front of it so it says drwxr-xr-x 3 root root 4096 Dec 31 16:00 . then under that it says drwx------ 6 root root 4096 Dec 31 16:03 .. then under that it says drwxr-xr-x 2 root root 4096 Mar 11 2017 System Volume Information that popped up after i typed the mount-o sync /dev/nandf /root/udisk and the ls-la /root/udisk yet the bash bunny serial console still has all of the files in it when i type ls for directories its all there. but when i manually go into the bash bunny as a drive it just says drive D: isn't called Bash Bunny anymore and there is nothing on the bunny except System Volume Information and the contents inside that. So howcome all the Bunny files are still their in the linux serial console but i can't access anything on the bunny and it's not even called Bash Bunny anymore and it is still Read Only
-
also does it flash green or blue because mine went from red to flashing blue
-
i did that and when i plugged it back into my computer it says 2.1 GB Volume and it is still Read only and it has no files at all on it it wont even let me put the old files back on it either but i'll try that again all i did in my linux box was click the reformat box and to keep all old files so i hope i didn't completely forever whipe it. because it wont even let me rename it and it says its read only so i hope it works this time
-
so i was trying to work on getting the quickcreds payload to work it kept stopping at the white blinking stating dependencies not met yet i had a tools installed.txt so i dont get why my dependencies werent met i was able to get other payloads to work then out of nowhere my bash bunny kept turning to read only and it kept saying something about dirty bit and i would correct it but same problem i couldn't copy anything to the bunny so as a last resort i formatted it now its rendered useless please help how do i fix this
Suggestion
in Bash Bunny
Posted
the idea is for the Bash Bunny to take less time to run the payloads. When the payloads are created they are created to take Seconds, even the QuickCredits one which gets you admin credentials of a locked PC takes 7seconds so there is no need to disguise the bunny from what it already is. It was a good thought though, most of the payloads take seconds to run and they are done.