Jump to content
Hak5 Forums

Darren Kitchen

Root Admin
  • Content count

    4,565
  • Joined

  • Last visited

  • Days Won

    143

About Darren Kitchen

  • Rank
    Hak5 Junkie
  • Birthday 02/11/1983

Contact Methods

  • AIM
    hak5darren
  • Website URL
    http://www.darrenkitchen.com
  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    San Francisco, CA

Recent Profile Visitors

91,656 profile views
  1. Unexpected LED patterns when upgrading 1.0 -> 1.1

    Your assessment is correct, the solid blue will be several minutes during the installation. Thanks for bringing this up. I've updated the documentation to reflect that the alternating red/blue pattern is when the firmware flash begins, which will be followed by a period of either a solid red or solid blue LED during the firmware installation.
  2. Firmware 1.1 and New Devices

    It was likely a USB formatting issue with the first flash drive. From testing I found that about one in a dozen USB drives, while formatted FAT32, did not contain a primary partition. This is technically against spec, but it works anyway. This was from a sampling of flash drives that had been collecting dust in my desk drawer from the various conferences over the years. The simple fix was to format them in GParted (NTFS or EXT4) with a partition table, rather than a generic block device. To make it even easier, Seb included a reformat_usb command on the Packet Squirrel that does the formatting for you.
  3. Serious Problem with Packet Squirrel

    St4L3y - TL;DR - I'm sorry - that shouldn't have happened. Please contact us, we'll send you a new one. We want to get hands on your broken one so we can do a proper autopsy. There's no good reason for your Packet Squirrel to act that way. Everything you described up until the point that it went LED silent sounded normal. In the odd case that a file got corrupted or something that prevented it from booting normally, the recovery procedure should have gotten you back up and running. That HTTP recovery console is part of the bootloader, which is in protected memory - so under normal circumstances nothing should be able to mess with it. That said, everything you've described thereafter indicate a more complex issue. We'll want to get it back in the lab for testing, to do proper failure analysis and see if there isn't something we can do on our end to prevent this sort of fault. Please head over to https://hakshop.com/contact and submit a warranty request. Include your order number, link to this thread and select Item Malfunctioning from the issues list. The Hak5 team will take care of the rest. Again, I'm really sorry for the fault and owe you thanks for detailing your troubleshooting process here. We'll get it sorted right away
  4. Why no power over ethernet ?

    These work pretty well too
  5. Pocket Squirrel work with WIFI Adapter?

    Yep, it's just a matter of adding the right /etc/config/network, /etc/config/wireless and /etc/config/firewall configs. Will make some time to do a write-up.
  6. [RELEASE] Packet Squirrel Firmware v1.1

    We wrote the release together, live in a Google doc. To be perfectly honest, I had expected Seb at some point to have jumped in and stopped the shenanigans - but... Here we are! On a more serious note however, it's awesome firmware so go try it :)
  7. Host unreachable

    Just to cover all bases, on your Windows computer go ahead and disconnect from all other networks (e.g. WiFi) so that when you connect to the Packet Squirrel in arming mode it's the only device available. Your Network Connections (from Control Panel) should look like this. My Network Interface Card connected to the Packet Squirrel is the ASIX AX8877B named "Ethernet 11" If you have a Wi-Fi connection, right-click it and choose Connect / Disconnect, then turn your Wi-Fi off. Next make sure your Packet Squirrel switch is flipped to the arming mode position. That's the position closest to the USB host port where a flash drive can plug in. Then power on your Packet Squirrel and connect an Ethernet cable between its "Ethernet In" port (that's the one right next to the Micro USB power port) and your computer. Then right-click your Ethernet adapter and select properties. You'll get a menu that looks like this: Click Details and you'll get a screen like this: And you should see next to IPv4 an address similar to mine -- 172.16.32.something If you don't see that, go ahead and close that menu and click Properties on the Ethernet Status window. From this menu: Select Internet Protocol Version 4 and click Properties And make sure on the following screen the adapter is set to obtain both IP and DNS automatically. Click OK twice and close once.
  8. PacketSquirrel + Printer Exploitation Toolkit

    On this topic, check out the LPR and DIPRINT protocols. With the tcpdump payload between a network printer and the rest of the LAN you'd be able to reassemble the print job. You'd be best to filter for just ports 515 and 9100. Here's some reading on it: http://rfg-esource.ricoh-usa.com/oracle/groups/public/documents/communication/rfg042515.pdf https://ask.wireshark.org/questions/27981/how-to-get-lpd-data-content https://www.backtrack-linux.org/forums/showthread.php?t=34435
  9. USB Storage

    Make sure the USB disk actually has a partition on it. I have a rather large collection of USB disks from conferences over the years. I keep 'em since many of 'em use the generic USB Rubber Ducky case, printed with company logos :) An odd thing I noticed while testing the Packet Squirrel prototype. A small number of disks couldn't be read, even after being formatted in either NTFS or EXT4. As it turns out, they had no partition at all - they were just a block device without a single partition. It was strange. After creating a partition with gparted or similar there wasn't an issue. Anyway - as you've discovered the reformat_usb command makes it right as rain.
  10. Packet Squirrel wiki repository

    Good call. In that case said auto-routing script could live on the VPN server side. As it turns out this same conundrum was sorted on a LAN Turtle thread regarding the OpenVPN-AS method I had previous stated
  11. LAN Turtle vs. Packet Squirrel

    You're forgetting Seb that it comes with the new LAN Turtle stickers, which makes it go faster =P
  12. Packet Squirrel wiki repository

    Wow - this is fantastic. I'll attempt to duplicate this with the Packet Squirrel ASAP. I've done similarly with the LAN Turtle on Hak5 using OpenVPN-AS and, I wouldn't say it was a nightmare, but it was nowhere near as straight forward as your write-up. Thank you! The only difficulty I see is that the OpenVPN server needs prior knowledge of the remote network's IP scheme -- in your example 192.168.0.0/24. In the event that one is dropping a Packet Squirrel on a network as part of a penetration test through means of social engineering, prior knowledge of the IP scheme may not be available. I wonder in that case if a script on the Packet Squirrel end could then enumerate the LAN before establishing the OpenVPN connection, and then pass over its own config to be used. Perhaps then "re-dialing" if need be.
  13. OpenVPN throughput / CPU Power ?

    It's what you'd expect from a low power embedded Linux box. About 5-6 Mbps. Initially the OpenVPN connection was just for remote access, but after nailing down that feature we figured, why not let the client tunnel through instead of just using it as a backdoor? Means you could setup any number of MITM frameworks/exploits on your VPS pentest box and sniff/meddle with the target's connection from afar. Or - ya know - use it to secure your own connection. Guess it depends on your hat
  14. [RELEASE] Bash Bunny Firmware v1.4

    Actually ADB may be a possible attack vector against some IoT junk
×