Draxiom

Also, autossh seems to have an extra 'port' field now. I've tried updating, uninstalling and reinstalling fresh, but it persists. I am also not able to get rid of the apostrophe in that field. If I set it to the local or remote port value, or erase it completely, the apostrophe is always tacked onto the end. I am not able to get an ssh connection through this module, and I suspect this extra field or rouge apostrophe is the problem. I can ssh to my host from a shell manually, but I do have to use the -oKexAlgorithms flag to set a diffie-helman handshake for my setup. I had this working on an earlier version of the firmware, so I could use some help. @Sebkinne

Is it a mythical creature? Is it a turret that shoots turtles? Or just a spelling mistake? ? Wasn't getting an IP on my turtle, so I decided run the recovery and saw this typo. Probably a known issue, and too late to fix now... but I thought it was funny, so there ya go.

Update: *hangs head in shame* I restarted the mac, and it started mounting again. Carry on like nothing happened.

Update: I realized that I didn't try plugging it into my linux box and was able to get it to mount on that. Got it all updated through the linux updater and everything works normally... on my linux box. On my mac, the bb still is not mounting. So my solution is to get rid of my mac. https://i.imgur.com/i3IfafU.gifv Anybody have an idea for me to avoid this?

Hey all, I have got my bb into a state that I can't seem to recover from and I was hoping for some help. Here's the scenario: I had just updated my bb using the bb updater on mac and confirmed the version number was up to date. Then, I was testing out the TARGET_OS and AUTO_ETHERNET flags (from this post: https://forums.hak5.org/topic/42465-release-bash-bunny-firmware-v15/?do=findComment&comment=301403) when the storage stopped mounting. It now does not mount on the host machine no matter what I have tried since. Here's what I have tried so far with no access to mounted drive from host: Switch to arming mode Simple payload with `ATTACKMODE STORAGE` as the only command on switch1 and switch2 Ran firmware recovery/reset Manually loaded udisk.sh script (local mount works, still never shows on host) https://forums.hak5.org/topic/41051-canøt-mount-nandf-how-to-completely-restore/?do=findComment&comment=291815 (re)formated udisk Added `ATTACKMODE SERIAL STORAGE` to /root/udisk/payloads/arming/payload.txt Tried to ics but could not get a connection to the outside world I can still: screen into bb in arming mode and with `ATTACKMODE SERIAL` on either switch position manually mount the nandf partition using the udisk script Trigger the basic LED commands that first came with the bb since I ran recovery, I am no longer on the latest firmware Note: I only have access to mac and linux. windows by vm only. Any thoughts on how I can get the mass storage mounting on my host computer in arming mode?

Also, if it doesn't start right away, you can blow (on) it:

caffeine helps

np. got mine at the event last night.

I tried, and it threw a usage error. Worked fine on a rpi, but couldn't get it to run on the squirrel. Dunno what about the syntax is wrong for this device. https://pastebin.com/PPF4k3pA

That makes sense.

Well considering you need to power it with micro usb, I doubt if it supports PoE at all.

Here's what mine says: https://pastebin.com/a6qGF5mg

I got you fam. Preshow: The main event: I was there. It was dope.

Hack all the things

Got mine