Join Date: Oct 2009
Location: 3rd Rock
Device(s): Motorola® DROID® BIONIC®
Thanked 1,918 Times in 1,362 Posts
Originally Posted by ndoren
John, good questions.
As it turns out, this is a VERY secure way to access your phone. Well, no more or less secure than accessing any linux box via ssh over the internet, which thousands of people do every day. There is no unbridled access to the phone. To log into the phone remotely, you need to supply a password (which you set up within the QuickSshd app).
There are no cables involved... every connection is done via 3G, and all connections are secure. The key is that you can be at one location, and your phone can be anywhere else in the country where it happens to have a 3G connection. In other words, your phone looks like some linux box out there on the internet somewhere, far away, and you remotely log into it. Of course, if your computer is next to your phone, just use a USB cable (or I use SMB/CIFS via wireless and just mount my PC drive to it without cables.
Consider this scenario: Assume someone wants shell access to their phone while at work, but they can't take their phone into the office (for whatever reason). From their car, they use ConnectBot (with port forwards set up) and ssh from their phone to some linux box at home or school. Then, they simply leave that connection active. So, yes John is right that it requires an active ssh connection from the phone to a linux box, and requires the phone to be running the QuickSshd app. No problem, just plug it into the cigarette lighter and fire that stuff up before you leave your car. The port forward involves mapping the sshd port on the phone (port 22) to some remote port on the distant machine (say port 8022).
Now, to access a shell on the phone, you ssh from your office to the linux box that your phone's ssh daemon is port forwarded to. Then once logged onto that machine, ssh to the localhost port (port 8022 in this case) on that machine and viola, you have a shell opened up to your phone.
So, here is the point. Your phone is one place (say, your car). You are another place (work), and you "meet" your phone at some third place, say your linux box at school. Neall
That definitely wfm. Especially the part I boldfaced - that is the important part - with that in place, you're right, no unbridled access.
Originally Posted by ndoren
Ok, so maybe that last example is a bit far fetched for you... because your phone is never far from your computer. My phone often is away from me, so I do use it as described above.
Here is a more practical application of SSH port forwarding, that I use every single day: Unlimited surveillance camera monitoring...
I have an IP-based surveillance camera on my local home network. I also have a desktop linux box on my home network. I can access the video camera via its web-access port 80 when at home via wifi. Now, when on the road, let's say I want to access my home webcam from my Droid. I can use the Seedonk app, but that app sucks because it only streams for a few minutes at a time, and Seedonk costs money. Instead, when on the road, I use ConnectBot on my Droid to ssh to my home linux machine, and I _reverse_ (aka remote) port forward the IP camera's web browser to a port on my Droid. Now, that makes the web cam look like it's attached directly to my Droid, when I'm actually hundreds of miles away! I then use the freebie IP Cam Viewer app (in the market) and tell it the cam is connected directly to my Droid (localhost) at the port I used in ConnectBot port forward. That way, I can have a continuous 24-hour webcam connection to my Droid via 3G without using payed servers with limited connect times.
Hope this all wasn't too confusing. Neall
Not for me it isn't lol. I have had enough experience with *nix to follow your gist.
I might look into this soon enough....