Search the Community
Showing results for tags 'packetsqurrel'.
The version of Cloud C2 is 3.1.2; Packet Squirrel is FW 3.2. When the Packet Squirrel is in Arming mode it is listed with the Uptime incrementing. When the Packet Squirrel is in Switch1 position the Uptime say Last Seen. The USB storage on the Packet Squirrel collects data from TCPDump OK when in postion 1. Any ideas on why, when the Packet Squirrel is in Switch1 position that the Cloud C2 Does not show it as Running? ~hbackus
Hey guys, First post 🙂 Anyways I really have been enjoying the Packet squirrel as a passive Vpn Out. Although I know that's not its intended purpose. Also great for monitoring network. I put it inbetween my modem and router and encrypted everything to a PIA server. Although small thing I have to hash out# disable-occ line of the config.ovpn . Was wondering if there was a way to re-enable this and getting the vpn to disable-occ, or if it's even needed at all? (Just wanna pick yall for some knowledge on this option) Any security issues I can expect running a packetsquirrel as a vpn out? It's very nice if you don't trust your ISP all that much, everything leaving the router to the modem can be encrpyted. Including Wifi, without needing to run openvpn on the client computers. Silly way to get around a client limit as well. 🙂 I am kind of rookie, but it works as advertised it's pretty impressive how simple it is. Seems like a much better way to tunnel in than using a raspberry pie as well. Thanks for a great product. 🙂
Since getting a PacketSquirrel and learning that it would be great to drop behind amongst other things printers it got me thinking. The PacketSquirrel already has some solid tools installed as default but figured PRET (Printer Exploitation Toolkit) would be a nice addition. Info on PRET https://github.com/RUB-NDS/PRET Recent Blackhat presentation https://www.blackhat.com/docs/us-17/thursday/us-17-Mueller-Exploiting-Network-Printers.pdf Other printer attack info http://hacking-printers.net/wiki/index.php/Main_Page known vulnerable printer databases here https://github.com/RUB-NDS/PRET/tree/master/db Mine wasn't in the db but worked with pcl so I'm sure others will work also. After some challenges squeezing it onto the PocketSquirrel without going full extroot I think I figured it out on the default squirrel build. I tried adding /mnt as a opkg destination and using links and then pip etc... but in the end manual install of python modules seems to have the lowest footprint. After install still leaving the PacketSquirrel with 55% of unused rootfs . I'm not 100% sure if this can be "payloaded" but at least for remote SSH access its a nice tool to have. My problem now is the printer I borrowed uses PCL and that in itself is quite restrictive in what can be done with PRET, so im kinda out of my testing limit and need other targets to test against so I'm sharing it here for others to try. The install method I used in the end was to plug my USB drive into my laptop and git cloned each of the following to the drive. https://github.com/RUB-NDS/PRET https://github.com/etingof/pysnmp https://github.com/etingof/pysmi https://github.com/etingof/pyasn1 https://github.com/tartley/colorama Once cloned unplug safely and replug back into your squirrel. Then EXCLUDING PRET, go into each dir and use python to install the modules "python setup.py install' afterwards you should then be able to run PRET and use its tools from the squirrel directly.