For how awesome Google Voice is, we’re surprised we haven’t seen this before. [Steve] is using Google Voice to run commands on just about any Linux box.
Google Voice doesn’t have an official API, and existing unofficial APIs weren’t up to snuff for [Steve]’s project. He ended up writing his own that checks his unread message inbox every minute and looks for new text messages beginning with the phrase, ‘Cmd’. If a series of checks pass – the text coming from a known phone number and a proper terminal command – the command runs and sends the a text back indicating success or failure.
While [Steve] probably won’t be playing nethack or Zork via SMS anytime soon, we can see this being very useful for a Raspi home automation task. Just send a text message and a properly configured Linux box can open your garage door, turn on the lights, or even start a webcam.
A pentesting dropbox is used to allow a pentester to remotely access and audit a network. The device is dropped onto a network, and then sets up a connection which allows remote access. As a final project, [Kalen] built the Rogue Pi, a pentesting dropbox based on the Raspberry Pi.
The Rogue Pi has a few features that make it helpful for pentesting. First off, it has a power on test that verifies that the installation onto the target network was successful. Since the install of a dropbox needs to be inconspicuous, this helps with getting the device setup without being detected. A LCD allows the user to see if the installation was successful without an additional computer or external display.
Once powered on, the device creates a reverse SSH tunnel, which provides remote access to the device. Using a reverse tunnel allows the device to get around the network’s firewall. Aircrack-ng has been included on the device to allow for wireless attacks, and a hidden SSID allows for wireless access if the wired network has issues. There is a long list of pentesting tools that have been built to run on the Pi.
Check out a video demonstration of the dropbox after the break.
Continue reading “Rogue Pi: A RPi Pentesting Dropbox”
[Ricard Dias] wrote in to tell us about his guide for developing Linux applications on a Mac. He really enjoys the development environment provided by XCode, and it doesn’t take much to make it work as an all-in-one solution for Linux development.
The real trick here is the use of SSH to access a Linux environment. In this example he uses Ubuntu running as a virtual machine, but also mentions that the same thing can be done just as easily with a separate box as long as it is on the same network as the Mac. SSHFS (the SSH Filesystem) lets him mount the development directory on the Linux box locally. This is where the XCode project and files will be stored, but building the program will be done by the Linux machine via a script calling the make comand via SSH. To test out the newly built program, [L] tunnels in using X11 forwarding for ssh, and the application will be shown as a window in OSX, even though it is running on the Ubuntu machine.
We love SSH and use it all the time. It’s amazing how hand it can be.
[Russ] was lucky enough to get his hands on a deeply discounted HP TouchPad, and after hearing about the huge bounty being offered for getting Android up and running on the device, he decided to poke around and see if he could make some headway.
He started off by making a full backup copy of his file system using a tool HP has on their WebOS site, just in case anything unfortunate happened to his device in the process. He grabbed a copy of the ARM cross-compiler and set off to build a copy of OpenSSH for the TouchPad. Once he had the binaries in hand, he started what he thought would be the arduous process of getting SSH onto the TouchPad, but it turned out that it was a simple drag and drop operation.
After remounting the file system to allow write operations, he fired up the SSH daemon and hoped for the best. It worked like a charm, and while it’s a relatively small part of getting Android running on the TouchPad, every bit helps.
Gather round and hear the story of how a hacker outsmarts a criminal. [Zoz] was robbed and they got his desktop computer. Gone, right? Nope. Because of a peculiar combination of his computer’s configuration, and the stupidity of the criminal, he got it back. He shares the tale during his Defcon 18 talk (PDF), the video is embedded after the break.
[Zoz’s] first bit of luck came because he had set up the machine to use a dynamic DNS service, updated via a script. Since the criminal didn’t wipe the hard drive he was able to find the machine online. From there he discovered that he could SSH into it, and even use VNC to eavesdrop on the new owner. This, along with a keylogger he installed, got him all the information he needed; the guy’s name, birth date, login and password information for websites, and most importantly his street address. He passed along this juicy data to police and they managed to recover the system.
Continue reading “A hacker’s marginal security helps return stolen computer”
The Seagate FreeAgent Dockstar aims to make all of your stuff available online. It serves that purpose but sometimes you just want more options for controlling your hardware and running some scripts. [Eric Cooper] put together a guide for installing OpenWRT on the Dockstar by building your own kernel and loading it onto the internal storage. Once you have a kernel that will play nicely with the hardware, you can install it by tunneling in through SSH; the same method you would use if you wanted to run Linux on this hardware. If you have problems along the way, [Eric’s] also included a guide for cracking the Dockstar open and connecting a serial cable.
Alright, so Doom isn’t actually running on the key chain itself, but rather a BifferBoard: a small 150MHz x86 containing ethernet, serial, and even USB with only one watt of power consumption! The project is to show how easy it is to program the BifferBoard and getting it talking to other hackable items – such as the picture key chain for a display. Doom does appear a bit slow, but [Biff] figures its do to how haphazardly it grabs keyboard input over SSH.