Jump to content


Root Admin
  • Posts

  • Joined

  • Days Won


Everything posted by Sebkinne

  1. Simply delete your database file (c2.db) and re-run the command. This will generate a new setup token for you. In the future we'll have it print a token until setup had been completed.
  2. We haven't abandoned anything, we just aren't that active there. It's a great place for the community to hang out though.
  3. For now we just released the ARM server, but in time we'll have clients available for BYO devices.
  4. This is not a bug, and changing the radio configuration will result in a lot of things breaking. We changed the default filter configuration a while back, which means by default all connections to wlan0 are denied. If you want to allow all devices to connect on any SSID, make sure both of your filters are empty and set to "Deny".
  5. Auto updates are currently unavailable for the arm version - unfortunately there isn't a way to detect which arm version the binary was compiled for right now, which is why we can't auto download. We'll release a fix for this shortly.
  6. Update: the ARM binaries are now part of the ZIP files in the download 🙂
  7. Hi CuChulaind, Please reach out to support at https://docs.hak5.org/hc/en-us/requests/new Best regards, Sebkinne
  8. Yup, that happens a lot, especially with WiFi drivers. Always research what chipset a wireless card uses and look up the driver compatibility before you buy ?
  9. You can navigate around as you please, recon scans will continue in the background and show you results when you get back to the recon module.
  10. No clue, sorry. Definitely not us ?
  11. Hi Oac, Currently the Cloud C2 server doesn't work properly behind a reverse proxy - we'll introduce settings which support this in the next update, which should be out within the week. Unfortunately, this doesn't seem to have anything to do with the fact the license cannot be validated. The message "error validating license key" means that there was an issue communicating with the c2.hak5.org server, or that the response was incomplete or corrupted. I'm going to see if I can replicate the issue. If I can we'll make sure it's fixed for the next update.
  12. Hi Oac, Does you docker container have network access to https://c2.hak5.org? As long as the server can reach that URL (and you have a valid license), you should be good to go.
  13. I can vouce for that link -- it's to the `Hacking Exposed` book :)
  14. We don't really support using the devices locally if they are set up to work with the C2. It can cause a bunch of possible synchronization issues, which is why we are considering disabling local access all together (when a device is registered with a C2 server). Before we do that though we want to make a few more options, such as networking, available via the C2.
  15. We'll check out what the driver difference was and see if we can get it working again!
  16. `-hostname localhost` is your issue. You'll want to put your computer's IP address there, otherwise devices will try to reach the server on "localhost".
  17. This is because the dashboard requests make the CPU spike to a high amount. The WiFi Pineapple NANO is not actually at 100% load. If you want to see more accurate statistics, please SSH into your WiFi Pineapple NANO and run the 'top' command.
  18. Seeing as we are re-shuffling a bunch of firmware code and pushing some more stuff upstream, I'll see if I can also add the WiFi Pineapple MKV to upstream OpenWrt. No promises, but that would at least allow you to build vanilla OpenWrt for it.
  19. We gave the MKV a few years before discontinuing it. We intend to keep support going for the WiFi Pineapple NANO and TETRA as long as it is feasible.
  20. Hi BeNe, Currently you are not going to be able to run the server in HTTPS mode with custom certificates / without the ACME client. An option allowing this is currently in the works. If you wanted to run the Hak5 C2 Server behind a reverse proxy (with SSL or without), we will need to add an option to override the C2 URL which the clients use, as this is currently done automatically and would break the client configuration. This is also something currently in the works. Both of these configurations will be available in the near future.
  21. Yup, this is also in the works!
  22. We'll be releasing ARM builds of the server in the very near future.
  • Create New...