sploders101

I’m just now seeing this as I’m going to bed, but I did fix this before posting here; I just wasn’t sure if it was the right way to fix it, but I haven’t experienced any issues thus far. I will plug in my shark jack tomorrow morning and post my exact configuration here so you can give it a try.

This is purely a high-level concept, and likely not something that could be done today, but I've been thinking about turning my Bash Bunny (arriving Friday) into a password manager, and I'd really like to keep those safe, so I was thinking that since the MKII has a bluetooth radio, you could potentially write a program that pairs with an app for decryption by phone. It would come online, ask your phone to decrypt or provide a payload, store it in RAM (using a tmpfs), and execute from there. Then, the moment it's turned off, it would disappear. Does anyone see any technical challenges with this other than the phone app? If you wanted to protect loot, that should be pretty trivial using gpg and a public/private keypair, with the public key being on the Bunny.

It is the Shark Jack Battery on firmware version 1.1.0-stable (the latest available for that model on downloads.hak5.org)

I just got my new Shark Jack in the mail today, and when I was playing around with it I realized it didn't have curl. I saw on the guide that it comes with opkg to install extra packages, but it seems to reference the 18.04-SNAPSHOT version in the OpenWRT repositories, which does not exist. I started looking through the packages, found some dates, and looked for the version that has "Last Modified" dates similar to the Shark Jack version, and settled on 18.04.1. However, I'm not sure if this is correct. So far, it's worked for libustream-mbedtls, ca-bundle, ca-certificates, nano, and curl, and seems to be fine. Can someone confirm this? Ideally, I'd like to see an official firmware update with fixed URLs, but this seems to work for now. Thanks!