FORUMS
Remove All Ads from XDA

[Q&A] [APP][INFO|SUPPORT] SSHelper (The free Android SSH Server Application)

n/a posts
Thanks Meter: 0
 
By QA Bot, Guest on 21st November 2014, 06:38 PM
Post Reply Email Thread
Q&A for [APP][INFO|SUPPORT] SSHelper (The free Android SSH Server Application)

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [APP][INFO|SUPPORT] SSHelper (The free Android SSH Server Application). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy!
 
 
29th December 2014, 02:19 AM |#2  
Junior Member
Thanks Meter: 0
 
More
PTY allocation request fails on Android 5 Lollipop
I love SSHelper. I allows me to use rsync, scp ans bash scripts to synchronize music and picture files back and forth between my Android device and a computer. I have been using it for a couple of months. Everything worked flawlessly. Life was great.

Now my Nexus 5 phone updated to Android 5 Lollipop and I have not been able to use SSHelper ever since. When I try to ssh my phone from an Apple computer (running Mac OS 10.9 or 10.10), I receive this error message:

Code:
PTY allocation request failed on channel 0
sh: /data/data/com.arachnoid.sshelper/home/.profile[2]: uname: not found
The connection process completes, but then I am not able to use most shell commands like ls, rsync, scp, etc.

The problems seems related to the new version of Android since I did not have that problem before. Yet a couple of Google searches indicates that few people have this problem. I try re-installing SSHelper, but I was already using the latest version (6.8). That didn’t help either. Any indication on how to solve the problem would be greatly appreciated. I can provide more information on the app behaviour if needed.
13th April 2015, 09:47 PM |#3  
Junior Member
Thanks Meter: 0
 
More
SSHelper interactive shell session problem solved.
Dear readers:

I'm the author of SSHelper, and until recently SEAndroid has been causing problems with interactive shell sessions. I have managed to fix this bug in SSHelper versions 7.1 and newer, details of which are located on the SSHelper home page (can't post a complete link to arachnoid.com/android/SSHelper).

In many cases, to see the full effect of this bug fix, you will need to uninstall and reinstall SSHelper.

Thanks for your patience.
28th June 2015, 06:16 AM |#4  
Junior Member
Thanks Meter: 1
 
More
Question Can't generate ssh host keys?
I'm brand new to Android and just got an Asus Transformer TF103C. I installed SSHelper via the Play Store, but am having trouble getting it to start. It seems it's having trouble generating the SSH host keys that the SSH server needs to start up. Any ideas on how to fix this? Log attached.

I think I'm running Android 4.4.2 with SSHelper 7.7

Code:
2015-06-28 01:08:25 execCom:executing: "/system/bin/id"
2015-06-28 01:08:25 execCom::stdout result: uid=10141(u0_a141) gid=10141(u0_a141) groups=1015(sdcard_rw),1028(sdcard_r),3002(net_bt),3003(inet),50141(all_a141) context=u:r:untrusted_app:s0
2015-06-28 01:08:25 execCom::exit value: true
2015-06-28 01:08:25 execCom:executing: "bin/ssh-keygen -t dsa -f /data/data/com.arachnoid.sshelper/home/.ssh/id_dsa -Y -q"
2015-06-28 01:08:25 execCom::exit value: false
2015-06-28 01:08:25 execCom:executing: "bin/ssh-keygen -t rsa -f /data/data/com.arachnoid.sshelper/home/.ssh/id_rsa -Y -q"
2015-06-28 01:08:25 execCom::exit value: false
2015-06-28 01:08:25 execCom:executing: "bin/ssh-keygen -t ecdsa -f /data/data/com.arachnoid.sshelper/home/.ssh/id_ecdsa -Y -q"
2015-06-28 01:08:25 execCom::exit value: false
2015-06-28 01:08:25 LogServer: restarting server on port: 8080
2015-06-28 01:08:25 execCom:executing: "bin/ssh-keygen -t dsa -f /data/data/com.arachnoid.sshelper/home/.ssh/id_dsa -Y -q"
2015-06-28 01:08:25 ClipboardServer: restarting server on port: 8081
2015-06-28 01:08:25 execCom::exit value: false
2015-06-28 01:08:25 execCom:executing: "bin/ssh-keygen -t rsa -f /data/data/com.arachnoid.sshelper/home/.ssh/id_rsa -Y -q"
2015-06-28 01:08:25 execCom::exit value: false
2015-06-28 01:08:25 execCom:executing: "bin/ssh-keygen -t ecdsa -f /data/data/com.arachnoid.sshelper/home/.ssh/id_ecdsa -Y -q"
2015-06-28 01:08:25 execCom::exit value: false
2015-06-28 01:08:25 Starting/restarting SSH server on port 2222
2015-06-28 01:08:26 sshd: Could not load host key: /data/data/com.arachnoid.sshelper/home/.ssh/id_dsa
2015-06-28 01:08:26 sshd: Could not load host key: /data/data/com.arachnoid.sshelper/home/.ssh/id_rsa
2015-06-28 01:08:26 sshd: Could not load host key: /data/data/com.arachnoid.sshelper/home/.ssh/id_dsa
2015-06-28 01:08:26 sshd: Could not load host key: /data/data/com.arachnoid.sshelper/home/.ssh/id_ecdsa
2015-06-28 01:08:26 sshd: Disabling protocol version 2. Could not load host key
2015-06-28 01:08:26 sshd: sshd: no hostkeys available -- exiting.
2015-06-28 01:08:26 * There are no SSH server hostkeys available.
2015-06-28 01:08:26 * to solve this problem, click the "Restart" menu item.
2015-06-28 01:08:26 LogServer: restarting server on port: 8080
2015-06-28 01:08:26 ClipboardServer: restarting server on port: 8081
2015-06-28 01:08:33 JmDNS Zeroconf:register service: _workstation._tcp.local
2015-06-28 01:08:36 JmDNS Zeroconf:register service: _sftp-ssh._tcp.local.
2015-06-28 01:08:38 JmDNS Zeroconf:register service: _ssh._tcp.local.
2015-06-28 01:08:41 JmDNS Zeroconf:register service: _rsync._tcp.local.
2015-06-28 01:08:43 JmDNS Zeroconf:register service: _http._tcp.local.
2015-06-28 01:09:13 LogServer: restarting server on port: 8080
2015-06-28 01:09:13 ClipboardServer: restarting server on port: 8081
2015-06-28 01:09:14 execCom:executing: "bin/ssh-keygen -t dsa -f /data/data/com.arachnoid.sshelper/home/.ssh/id_dsa -Y -q"
2015-06-28 01:09:14 execCom::exit value: false
2015-06-28 01:09:14 execCom:executing: "bin/ssh-keygen -t rsa -f /data/data/com.arachnoid.sshelper/home/.ssh/id_rsa -Y -q"
2015-06-28 01:09:14 execCom::exit value: false
2015-06-28 01:09:14 execCom:executing: "bin/ssh-keygen -t ecdsa -f /data/data/com.arachnoid.sshelper/home/.ssh/id_ecdsa -Y -q"
2015-06-28 01:09:14 execCom::exit value: false
2015-06-28 01:09:14 Starting/restarting SSH server on port 2222
2015-06-28 01:09:14 LogServer: restarting server on port: 8080
2015-06-28 01:09:14 sshd: Could not load host key: /data/data/com.arachnoid.sshelper/home/.ssh/id_dsa
2015-06-28 01:09:14 sshd: Could not load host key: /data/data/com.arachnoid.sshelper/home/.ssh/id_rsa
2015-06-28 01:09:14 sshd: Could not load host key: /data/data/com.arachnoid.sshelper/home/.ssh/id_dsa
2015-06-28 01:09:14 sshd: Could not load host key: /data/data/com.arachnoid.sshelper/home/.ssh/id_ecdsa
2015-06-28 01:09:14 sshd: Disabling protocol version 2. Could not load host key
2015-06-28 01:09:14 sshd: sshd: no hostkeys available -- exiting.
2015-06-28 01:09:14 * There are no SSH server hostkeys available.
2015-06-28 01:09:14 * to solve this problem, click the "Restart" menu item.
2015-06-28 01:09:14 ClipboardServer: restarting server on port: 8081
2015-06-28 01:09:17 LogServer: restarting server on port: 8080
2015-06-28 01:09:17 ClipboardServer: restarting server on port: 8081
31st January 2016, 05:35 AM |#5  
Junior Member
Thanks Meter: 0
 
More
This could quite possibly be PEBKAC (problem exists between keyboard and chair), but it seems strange enough that I thought I'd throw it out here to see if anyone else has run into this issue. In any case, I love SSHelper; it has come in handy numerous times. That said, one day I got warnings that my nexus 5 was running out of space. When I checked out "Apps" under "Settings" and sorted the apps by size, SSHelper jumped to the top @ 8.34GB! Initially I though it was because Android was misinterpreting the symlink to the SD Card in "home", but upon further analysis it appeared that at some point a bunch of data (Pictures, Videos, app folders, etc.) was copied into the /data/data/com.arachnoid.sshelper directory. One additional piece of that puzzle that leads me to believe that I might not have inflicted this on myself is the fact that all of the files that were copied seem to be missing the first letter of their filename, for example IMG_20140913_113434.jpg in the standard pictures location shows up as MG_20140913_113434.jpg (note the missing I in the beginning) in /data/data/com.arachnoid.sshelper. Anyone experience anything similar or am I just crazy?
19th April 2018, 04:45 PM |#6  
Junior Member
Thanks Meter: 0
 
More
I'm sorry to be replying to such an old thread, but I just noticed it because of a similar inquiry on my website. I'm the author of SSHelper, which uses some ARM-processor binaries to provide Secure Shell functions on Android devices. The Asus Transformer uses an Intel Atom processor, which is derived from the x86 processor family, not compatible with the ARM family.

Sorry -- it's a case of binary-code incompatibility.
Post Reply Subscribe to Thread

Tags
auto-qa

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes