Sebkinne

So our Cloudflare setup blocked your request because it detected a RCE attack. No idea why that would trigger from some links in the post, but I would suggest you try posting them again.

?

I'd probably use something like external merge-sort for this, but a database like @noncenz suggested should be a good choice for this.

From time to time Hak5 releases firmware updates for the Bash Bunny including new features, bug fixes and security improvements. The easiest way to install these is with the Bash Bunny updater. Available for Windows, Mac and Linux – this utility will automatically update your Bash Bunny to the latest software version. The payload library on the Bash Bunny can also be kept up to date using this tool. When the updater runs it will not only check for firmware updates (and updates to the utility itself), it will also synchronize your copy of the /payloads/library folder with the official repository. Additionally it will update any available language files. Find out more at https://bashbunny.com/setup

Yeah, it gave us a good laugh :)

Hey jeffrey, We are actually close to releasing a new WiFi Pineapple firmware which will feature a bunch of improvements to the base system and webinterface. Our current plan is to put the updated webinterface up on GitHub, so that community members like yourself can contribute to it properly. While I respect your desire to create a new interface, I would encourage you to contribute to the existing one instead. We could use any extra pairs of eyes, and are happy about all contributions.

Definitely not us. Thanks!

It's actually accurate - the animation just makes it seem like it's going too fast :)

Will fix this, thanks!

Hey everyone, We have recently discovered a bug in the update process of the Bash Bunny, which causes boot-loops. The bug is triggered if the upgrade file had been extracted, renamed, or was otherwise altered. Fortunately, we have now found a fix for the issue: Plug in the Bash Bunny and unplug it immediately when the initial green LED turns off Repeat step #1 three times Plug the Bash Bunny back in and wait for it to reset. You should see either a "police" pattern or a red blinking LED. Set the switch to the switch1 position (furthest from the USB port) Wait for the device to reboot (indicated by the green led) and set the switch to arming mode immediately as the green light turns off. If all went well, you should now be able to access the Mass Storage partition of the Bash Bunny (or serial in). Delete any leftover update files (such as "ch_fw_1.3_264 (1).tar.gz") Safely eject / sync the Bash Bunny Reboot your device, by re-plugging it, while keeping the switch in arming mode. This should get your Bash Bunny up-and-running on firmware v1.0, allowing you to properly upgrade to the latest version. We recommend using the Bash Bunny Updater for this. We have released firmware 1.4 which prevents this bug from being triggered. Note: These instructions are not the same as the one from this thread. Similar, but more reliable.

Interesting. If I can confirm this issue, we'll get it fixed and pushed out Friday.

This was a very entertaining read. Thanks for the chuckle.

You need to put it in quotes. An argument ending in .txt is going to be interpreter as ducky script. Not really a bug, but something we can work around in a future update.

The male USB on the WiFi Pineapple is the ethernet interface. It will enumerate as such on the host computer.

I have to say that I agree with Foxtrot here. We are currently working on centralizing a lot of our resources, so it would be super helpful to expand the current official wikis instead of having yet another place to find information. That way, we'll be able to serve the community better.

Not totally correct - we are still exploring how we can best get our offerings on Amazon.

Ignoring the sarcasm, imagine unstable extroot on "unstable" sd cards..

Extroot isn't stable enough unfortunately.

+1

All packages are packed in the hak5 warehouse in California. This is rather odd though, and I am looking into it.

Dual booting an SSD does not decrease it's lifespan. It's not like the SSD is now running two operating system simultaneously or is required to write more often than it would need to for the individuall OS.

Update your config.txt file (on your mass storage partition) to say "DUCKY_LANG de" instead of "DUCKY_LANG us". Also remove any mentions of DUCKY_LANG from the payloads you are running. In theory, no payloads should set the language at all, as this should now be done via the config.txt.

@HarambeCute Please do not double post (this thread existed three times), and please do not use bunny_helpers anymore. They are now "extensions" and can be found in the Bash Bunny Payload repository.

In all seriousness, I think it's something to do with the fact that we can enable Q/A type forum categories. This means people can "upvote" answers to a question. If you don't want to upvote but show appreciation, you can like instead -- I think.