Page 1 of 2 12 LastLast
Results 1 to 20 of 30
  1.    #1  
    Hi all,
    I've installed (via preware), OpenSSH and associated files, but have yet to be able to connect to the touchpad.

    Following all of the same procedures (from the WebOSInternals wiki), lets me get it working without a problem on my FrankenPre2, but not on the touchpad.

    Any advice from anyone who has it working?

    Thanks
    baldric
  2. #2  
    I had to redo my keys. Not sure why, but I wasn't able to just copy over an old key pair and reuse them. Did you get stuck on any particular step or it's just not working?
  3. #3  
    You sure you .ssh/authorized_keys is in root's $HOME? The first time I did it, I mistakenly put it in "/". Also, some sshd configs require 'chmod og-rwx .ssh'
  4.    #4  
    Howdy,
    No not stuck, its just not working. After not getting it to work on the touchpad (twice), I then tried on the pre2 and it worked like a charm. That's why I thought I'd ask here in case there was some special case with the touchpad.

    Thanks
    baldric

    Quote Originally Posted by appsotutely View Post
    I had to redo my keys. Not sure why, but I wasn't able to just copy over an old key pair and reuse them. Did you get stuck on any particular step or it's just not working?
  5. #5  
    Since I put 2.1.0 on my original Pre, I've had ssh issues. The wiki has you set the port to 222 (I think, been awhile and I use a different port). I can ssh in if I use "ssh -p 22 root@<ip>." which means that ssh is working, but not setting the right port. It's still using the default. I'm still looking around, but you may want the try the -p 22 to see if it's the same problem.
  6. #6  
    Quote Originally Posted by Chriswhat21Pre View Post
    Since I put 2.1.0 on my original Pre, I've had ssh issues. The wiki has you set the port to 222 (I think, been awhile and I use a different port). I can ssh in if I use "ssh -p 22 root@<ip>." which means that ssh is working, but not setting the right port. It's still using the default. I'm still looking around, but you may want the try the -p 22 to see if it's the same problem.
    This is the difference between installing OpenSSH using the instructions on the WebOS Internals website and using the Preware packages. The default port that the ssh daemon listens on is 22. The WOI setup throws in a little "security by obscurity" as well and has it listening on port 222.

    You also need to be careful of the permissions on your ~/.ssh directory. Something I just discovered is that when you mount your WebOS device as a USB drive, it acts exactly like a USB stick, including everything in /media/internal being world writable. When ssh keys and configuration directories are involved, that's a big "oops". (and also a big d'oh! for me personally)
  7.    #7  
    I tried un-installing and reinstalling openssh and opensftp based on the suggestion, and either that, or the updated optware bootstrap i installed today got it working.

    Thanks to everyone for helping out.

    baldric
  8. lordbah's Avatar
    Posts
    341 Posts
    Global Posts
    435 Global Posts
    #8  
    Huh. I had OpenSSH installed and working. Today I can't connect. Nova in and find the process isn't running. Look at Preware and it says OpenSSH is installed. Restart, still not running, no match for "ssh" in /var/log/messages, don't know what happened.

    start mobi.optware.openssh

    and it's running again. For some reason it apparently isn't starting when the device restarts.
  9. #9  
    +1 same problem here. I'm going to uninstall and reinstall to see if that fixes anything.

    edit: Reinstall fixed the issues with starting when the touchpad restarts.
    Last edited by peterlemonjello; 07/20/2011 at 09:23 AM.
  10. #10  
    Quote Originally Posted by lordbah View Post
    Huh. I had OpenSSH installed and working. Today I can't connect. Nova in and find the process isn't running. Look at Preware and it says OpenSSH is installed. Restart, still not running, no match for "ssh" in /var/log/messages, don't know what happened.

    start mobi.optware.openssh

    and it's running again. For some reason it apparently isn't starting when the device restarts.
    I'm having exact same symptoms, where sshd doesn't consistently start and stay running on bootup. The service starts just fine when I run the above command. The only difference is, I did find some interesting logs in /var/log/messages. Here's a relevant snippet:

    Code:
    2011-08-18T07:30:10.525260Z [18] webos-device daemon.info upstart: (00018/301100297) Handling started event
    2011-08-18T07:30:10.539843Z [18] webos-device daemon.warning upstart: (00018/315520741) mobi.optware.openssh main process (1993) terminated with status 2
    2011-08-18T07:30:10.540072Z [18] webos-device daemon.warning upstart: (00018/315688593) mobi.optware.openssh main process ended, respawning
    2011-08-18T07:30:10.540193Z [18] webos-device daemon.info upstart: (00018/315765778) mobi.optware.openssh state changed from running to stopping
    2011-08-18T07:30:10.540310Z [18] webos-device daemon.info upstart: (00018/315898963) Handling stopping event
    2011-08-18T07:30:10.540424Z [18] webos-device daemon.info upstart: (00018/316048000) mobi.optware.openssh state changed from stopping to killed
    2011-08-18T07:30:10.540538Z [18] webos-device daemon.info upstart: (00018/316132000) mobi.optware.openssh state changed from killed to post-stop
    2011-08-18T07:30:10.540650Z [18] webos-device daemon.info upstart: (00018/316204889) mobi.optware.openssh state changed from post-stop to starting
    2011-08-18T07:30:10.540765Z [18] webos-device daemon.warning upstart: (00018/316276445) mobi.optware.openssh respawn_count: 11 > respawn_limit: 10
    2011-08-18T07:30:10.540880Z [18] webos-device daemon.warning upstart: (00018/316345186) mobi.optware.openssh respawning too fast, stopped
    2011-08-18T07:30:10.541000Z [18] webos-device daemon.info upstart: (00018/316411852) mobi.optware.openssh goal changed from start to stop
    2011-08-18T07:30:10.541118Z [18] webos-device daemon.info upstart: (00018/316483408) mobi.optware.openssh state changed from starting to waiting
    2011-08-18T07:30:10.541549Z [18] webos-device daemon.info upstart: (00018/316578667) Handling stopped event
    It appears that, every time sshd respawns, it'll immediately terminate with status 2, but I can't figure out why. It happens 10 times and then gives up.

    Uninstalling and reinstalling do not help. I tried installing Dropbear, and I have the same issue there.

    Does anybody have any ideas? Thanks!
  11. #11  
    having the same problem here on my Touchpad running Warthog kernel ... openssh (sshd) sometimes starts at boot, other times it does not. It's easy enough to get running by launching it through xterm, but it would sure be nice if it worked and started by itself all the same.

    LC
  12. #12  
    Hi Guys,

    I am having a different issue. When i try to putty into my touchpad I get the following error;

    Disconnected: No Supported authentication methods available (server sent: publickey.keyboard-interactive)

    When I ssh into the touchpad throuch novaterm I get the following;

    ssh localhost
    The authenticity of host 'localhost (127.0.0.1)' can't be established.
    RSA key fingerprint is xx:xx:xx:Xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx.
    Are you sure you want to continue connecting (yes/no)? yes


    Warning: Permanently added 'localhost' (RSA) to the list of known hosts.
    Permission denied (publickey,keyboard-interactive).

    Any help would be appreciated.

    Edit: Okay, got it working. I had to export the key. Follow these instructructions if you have the same issue that I did. http://www.webos-internals.org/wiki/Application:OpenSSH
    Last edited by ewalker101; 09/05/2011 at 04:15 PM.
  13. #13  
    For me, SSH worked fine. Today when I went to use it, I keep getting a connection refused error message. starting and stopping the aforementioned process does not fix the problem, nor does restarting the device.

    What would cause it to suddenly stop working?
  14. #14  
    Kind of a pain. Have to start it through XTerm every time I want access. Hoping for a permanent fix.
  15. larizzo's Avatar
    Posts
    25 Posts
    Global Posts
    32 Global Posts
    #15  
    Also having same issue where it doesn't start consistently have to start it with xterm. Please update if you find fix.
  16. #16  
    For me, it appears to start correctly, just denies my connections. I'll probably just uninstall it alltogether
  17. #17  
    For anyone who got the respawn or sshd unable to start , you can fix it by modifying the upstart script mobi.optware.openssh either :

    1) add "sleep 10" into pre-start section
    or
    2) change "start on stopped finish" to "start on started up LunaReady" at the begining of the script.
  18. #18  
    Quote Originally Posted by luvu43v3r View Post
    For anyone who got the respawn or sshd unable to start , you can fix it by modifying the upstart script mobi.optware.openssh either :

    1) add "sleep 10" into pre-start section
    or
    2) change "start on stopped finish" to "start on started up LunaReady" at the begining of the script.

    It looks to me like sshd is trying to start too early with the default "start on stopped finish" line or the older "start on stopped finish and started org.webosinternals.optware" version.

    Adding the "sleep 10" will make each restart take a LONG time, and hopefully one of the 11 tries will be late enough that it will work.

    "start on started up LunaReady" seems to be incorrect syntax.

    "start on started LunaReady" seems to work for me with no "sleep 10"
  19. #19  
    Having the same problem here. Will try editing the upstart script. Frak I friggin' *hate* upstart! Sysv is so much cleaner and easy to understand / troubleshoot.

    *update*
    "start on started LunaReady" works here. No sleep necessary.
    Last edited by knobbysideup; 10/27/2011 at 03:54 PM.
    : (){:|:&};:
  20. jc-Treo's Avatar
    Posts
    439 Posts
    Global Posts
    444 Global Posts
    #20  
    I had the same issue regarding openssh not starting. Modified the upstart script in /var/palm/event.d to use script rather than exec, and added a sleep for 20 before starting the daemon and it works consistently now. I think I PM'ed the maintainer of the issue, but never heard back. Also, I did not notice that this slows down boot up.

    #exec
    script
    sleep 20
    /opt/sbin/sshd -D -p 222
    # Commented out the next because I I set a password for root and do not use keys
    # -o "PasswordAuthentication no" -o "PermitRootLogin without-password"
    end script
    Sprint Treo 650 --> Sprint Treo 700p --> Sprint Centro --> Sprint Pre- --> AT&T Veer/ Pre 2/ Pre 3, Touchpad
Page 1 of 2 12 LastLast

Posting Permissions